Message	SHA1
[ARM] Fix stacktrace FP range checking ... Fix an oops in the stacktrace code, caused by improper range checking. We subtract 12 off 'fp' before testing to see if it's below the low bound. However, if 'fp' were zero before, it becomes a very large positive number, causing this test to succeed where it should fail. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Russell King   commited 2007-05-30 13:15:12 +01:00	5b10c8e436
arm: walk_stacktrace() needs to be exported ... oprofile depends on having it Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Al Viro   authored and   Linus Torvalds   commited 2007-05-15 18:56:37 -07:00	7b104bcb8e
[ARM] stacktrace fix ... ab1b6f03a1 said - remove the unused task argument to save_stack_trace, it's always current then broke arm: arch/arm/kernel/stacktrace.c:56: error: conflicting types for 'save_stack_trace' include/linux/stacktrace.h:11: error: previous declaration of 'save_stack_trace' was here arch/arm/kernel/stacktrace.c:56: error: conflicting types for 'save_stack_trace' include/linux/stacktrace.h:11: error: previous declaration of 'save_stack_trace' was here Cc: Christoph Hellwig <hch@lst.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Andrew Morton   authored and   Russell King   commited 2007-05-11 17:38:50 +01:00	fac0779029
[ARM] Add stacktrace support and make oprofile use it ... Add support for stacktrace. Use the new stacktrace code with oprofile instead of it's version; there's no point having multiple versions of stacktracing in the kernel. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Russell King   commited 2007-04-28 09:59:37 +01:00	f16fb1ecc5