diff options
author | Konstantin Khlebnikov <k.khlebnikov@samsung.com> | 2013-12-05 13:21:36 (GMT) |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-12-20 15:48:51 (GMT) |
commit | 55727f26e32962c2e516bbebae1640feb3bc5b20 (patch) | |
tree | 2f5ff592c9aafbd1684b84646a948dd7520ebb91 /scripts/ksymoops | |
parent | 3c14b0b4d0553f2bd1325bce20a551d6e9350a26 (diff) | |
download | linux-fsl-qoriq-55727f26e32962c2e516bbebae1640feb3bc5b20.tar.xz |
ARM: 7912/1: check stack pointer in get_wchan
commit 1b15ec7a7427d4188ba91b9bbac696250a059d22 upstream.
get_wchan() is lockless. Task may wakeup at any time and change its own stack,
thus each next stack frame may be overwritten and filled with random stuff.
/proc/$pid/stack interface had been disabled for non-current tasks, see [1]
But 'wchan' still allows to trigger stack frame unwinding on volatile stack.
This patch fixes oops in unwind_frame() by adding stack pointer validation on
each step (as x86 code do), unwind_frame() already checks frame pointer.
Also I've found another report of this oops on stackoverflow (irony).
Link: http://www.spinics.net/lists/arm-kernel/msg110589.html [1]
Link: http://stackoverflow.com/questions/18479894/unwind-frame-cause-a-kernel-paging-error
Signed-off-by: Konstantin Khlebnikov <k.khlebnikov@samsung.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/ksymoops')
0 files changed, 0 insertions, 0 deletions