linux-toradex.git/kernel, branch v2.6.35-rc6

sysrq,kdb: Use __handle_sysrq() for kdb's sysrq function

2010-07-22T00:27:07+00:00

The kdb code should not toggle the sysrq state in case an end user
wants to try and resume the normal kernel execution.

Signed-off-by: Jason Wessel 
Acked-by: Dmitry Torokhov

debug_core,kdb: fix kgdb_connected bit set in the wrong place

2010-07-22T00:27:07+00:00

Immediately following an exit from the kdb shell the kgdb_connected
variable should be set to zero, unless there are breakpoints planted.
If the kgdb_connected variable is not zeroed out with kdb, it is
impossible to turn off kdb.

This patch is merely a work around for now, the real fix will check
for the breakpoints.

Signed-off-by: Jason Wessel

Fix merge regression from external kdb to upstream kdb

2010-07-22T00:27:06+00:00

In the process of merging kdb to the mainline, the kdb lsmod command
stopped printing the base load address of kernel modules.  This is
needed for using kdb in conjunction with external tools such as gdb.

Simply restore the functionality by adding a kdb_printf for the base
load address of the kernel modules.

Signed-off-by: Jason Wessel

repair gdbstub to match the gdbserial protocol specification

2010-07-22T00:27:05+00:00

The gdbserial protocol handler should return an empty packet instead
of an error string when ever it responds to a command it does not
implement.

The problem cases come from a debugger client sending
qTBuffer, qTStatus, qSearch, qSupported.

The incorrect response from the gdbstub leads the debugger clients to
not function correctly.  Recent versions of gdb will not detach correctly as a result of this behavior.

Signed-off-by: Jason Wessel 
Signed-off-by: Dongdong Deng

kdb: break out of kdb_ll() when command is terminated

2010-07-22T00:27:05+00:00

Without this patch the "ll" linked-list traversal command won't
terminate when you hit q/Q.

Signed-off-by: Martin Hicks 
Signed-off-by: Jason Wessel

kmemleak: Add support for NO_BOOTMEM configurations

2010-07-19T10:54:15+00:00

With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
friends use the early_res functions for memory management when
NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
corresponding code paths for bootmem allocations.

Signed-off-by: Catalin Marinas 
Acked-by: Pekka Enberg 
Acked-by: Yinghai Lu 
Cc: H. Peter Anvin 
Cc: stable@kernel.org

module: initialize module dynamic debug later

2010-07-05T03:17:22+00:00

We should initialize the module dynamic debug datastructures
only after determining that the module is not loaded yet. This
fixes a bug that introduced in 2.6.35-rc2, where when a trying
to load a module twice, we also load it's dynamic printing data
twice which causes all sorts of nasty issues. Also handle
the dynamic debug cleanup later on failure.

Signed-off-by: Yehuda Sadeh 
Signed-off-by: Rusty Russell  (removed a #ifdef)
Signed-off-by: Linus Torvalds

Merge branch 'sched-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

2010-07-02T16:52:58+00:00

* 'sched-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
  sched: Cure nr_iowait_cpu() users
  init: Fix comment
  init, sched: Fix race between init and kthreadd

sched: Cure nr_iowait_cpu() users

2010-07-01T07:39:48+00:00

Commit 0224cf4c5e (sched: Intoduce get_cpu_iowait_time_us())
broke things by not making sure preemption was indeed disabled
by the callers of nr_iowait_cpu() which took the iowait value of
the current cpu.

This resulted in a heap of preempt warnings. Cure this by making
nr_iowait_cpu() take a cpu number and fix up the callers to pass
in the right number.

Signed-off-by: Peter Zijlstra 
Cc: Arjan van de Ven 
Cc: Sergey Senozhatsky 
Cc: Rafael J. Wysocki 
Cc: Maxim Levitsky 
Cc: Len Brown 
Cc: Pavel Machek 
Cc: Jiri Slaby 
Cc: linux-pm@lists.linux-foundation.org
LKML-Reference: <1277968037.1868.120.camel@laptop>
Signed-off-by: Ingo Molnar

futex: futex_find_get_task remove credentails check

2010-06-30T22:43:44+00:00

futex_find_get_task is currently used (through lookup_pi_state) from two
contexts, futex_requeue and futex_lock_pi_atomic.  None of the paths
looks it needs the credentials check, though.  Different (e)uids
shouldn't matter at all because the only thing that is important for
shared futex is the accessibility of the shared memory.

The credentail check results in glibc assert failure or process hang (if
glibc is compiled without assert support) for shared robust pthread
mutex with priority inheritance if a process tries to lock already held
lock owned by a process with a different euid:

pthread_mutex_lock.c:312: __pthread_mutex_lock_full: Assertion `(-(e)) != 3 || !robust' failed.

The problem is that futex_lock_pi_atomic which is called when we try to
lock already held lock checks the current holder (tid is stored in the
futex value) to get the PI state.  It uses lookup_pi_state which in turn
gets task struct from futex_find_get_task.  ESRCH is returned either
when the task is not found or if credentials check fails.

futex_lock_pi_atomic simply returns if it gets ESRCH.  glibc code,
however, doesn't expect that robust lock returns with ESRCH because it
should get either success or owner died.

Signed-off-by: Michal Hocko 
Acked-by: Darren Hart 
Cc: Ingo Molnar 
Cc: Thomas Gleixner 
Cc: Nick Piggin 
Cc: Alexey Kuznetsov 
Cc: Peter Zijlstra 
Signed-off-by: Linus Torvalds