summaryrefslogtreecommitdiff
path: root/arch/arm/mach-ns9xxx/mach-cc9p9360dev.c
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2008-07-13 23:42:44 +0400
committerIngo Molnar <mingo@elte.hu>2008-07-13 23:50:46 +0400
commit4f962d4d65923d7b722192e729840cfb79af0a5a (patch)
tree33576a5a4093f2f937dd40be899d92982f6232bd /arch/arm/mach-ns9xxx/mach-cc9p9360dev.c
parentaf9ff7868f0f76d3364351b1641b9dfa99588e77 (diff)
downloadlinux-4f962d4d65923d7b722192e729840cfb79af0a5a.tar.xz
stackprotector: remove self-test
turns out gcc generates such stackprotector-failure sequences in certain circumstances: movq -8(%rbp), %rax # D.16032, xorq %gs:40, %rax #, jne .L17 #, leave ret .L17: call __stack_chk_fail # .size __stack_chk_test_func, .-__stack_chk_test_func .section .init.text,"ax",@progbits .type panic_setup, @function panic_setup: pushq %rbp # note that there's no jump back to the failing context after the call to __stack_chk_fail - i.e. it has a ((noreturn)) attribute. Which is fair enough in the normal case but kills the self-test. (as we cannot reliably return in the self-test) Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/arm/mach-ns9xxx/mach-cc9p9360dev.c')
0 files changed, 0 insertions, 0 deletions