LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: pageexec@freemail.hu
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: vmsplice exploits, stack protector and Makefiles
Date: Wed, 13 Feb 2008 18:15:13 +0200 [thread overview]
Message-ID: <47B333B1.28931.A31602E@pageexec.freemail.hu> (raw)
In-Reply-To: <20080213164853.GA25476@elte.hu>
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
>
next prev parent reply other threads:[~2008-02-13 17:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 17:00 Arjan van de Ven
2008-02-12 18:50 ` Sam Ravnborg
2008-02-12 19:08 ` Arjan van de Ven
2008-02-12 19:36 ` Sam Ravnborg
2008-02-13 13:38 ` pageexec
2008-02-13 15:29 ` Ingo Molnar
2008-02-13 16:29 ` Randy Dunlap
2008-02-13 15:48 ` pageexec
2008-02-14 12:20 ` Jan Engelhardt
2008-02-13 16:48 ` Ingo Molnar
2008-02-13 16:15 ` pageexec [this message]
2008-02-14 6:16 ` Ingo Molnar
2008-02-14 7:30 ` Ingo Molnar
2008-02-14 10:23 ` pageexec
2008-02-13 15:53 ` Linus Torvalds
2008-02-13 16:01 ` Ingo Molnar
2008-02-13 17:16 ` Sam Ravnborg
2008-02-14 6:12 ` Ingo Molnar
2008-02-14 7:43 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B333B1.28931.A31602E@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--subject='Re: vmsplice exploits, stack protector and Makefiles' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).