diff options
author | Ingo Molnar <mingo@elte.hu> | 2008-07-13 21:42:44 +0200 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-07-13 21:50:46 +0200 |
commit | 4f962d4d65923d7b722192e729840cfb79af0a5a (patch) | |
tree | 33576a5a4093f2f937dd40be899d92982f6232bd /kernel/kmod.c | |
parent | af9ff7868f0f76d3364351b1641b9dfa99588e77 (diff) | |
download | linux-4f962d4d65923d7b722192e729840cfb79af0a5a.tar.gz linux-4f962d4d65923d7b722192e729840cfb79af0a5a.tar.bz2 linux-4f962d4d65923d7b722192e729840cfb79af0a5a.zip |
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 'kernel/kmod.c')
0 files changed, 0 insertions, 0 deletions