Re: vmsplice exploits, stack protector and Makefiles
From: pageexec
Date: Wed Feb 13 2008 - 12:16:18 EST
On 13 Feb 2008 at 17:48, Ingo Molnar wrote:
> hm, had to pull it again because it crashed in testing:
i've only tested .24, not .25 so maybe something changed. did you
make sure that
write_pda(stack_canary, next_p->stack_canary);
was removed from arch/x86/kernel/process_64.c:__switch_to? that's
the only reason i can think of that would trigger this trace.
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
> Brought up 2 CPUs
> stack corrupted in: thread_return+0xd0/0xe2
> Pid: 0, comm: swapper Not tainted 2.6.25-rc1 #3
>
> Call Trace:
> [<ffffffff80242018>] __stack_chk_fail+0x2a/0x68
> [<ffffffff807a0478>] thread_return+0xd0/0xe2
> [<ffffffff8025f5c3>] getnstimeofday+0x3f/0xab
> [<ffffffff8025cfc7>] ktime_get_ts+0x27/0x6f
> [<ffffffff8025d02b>] ktime_get+0x1c/0x66
> [<ffffffff802639af>] tick_nohz_stop_idle+0x39/0x76
> [<ffffffff8020b204>] cpu_idle+0xb6/0xca
>
> Kernel panic - not syncing: stack-protector: Kernel stack is corrupted
>
> config attached.
>
> Ingo
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/