From: Andrew Morton <akpm@osdl.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: "In Cognito" <defend.the.world@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Sysenter crash with Nested Task Bit set
Date: Sun, 17 Sep 2006 22:25:37 -0700 [thread overview]
Message-ID: <20060917222537.55241d19.akpm@osdl.org> (raw)
In-Reply-To: <200609172354_MC3-1-CB7A-58ED@compuserve.com>
On Sun, 17 Sep 2006 23:51:45 -0400
Chuck Ebbert <76306.1226@compuserve.com> wrote:
> In-Reply-To: <5a20704e0609171608o7ee45fdbxb94aa897c1776153@mail.gmail.com>
>
> On Sun, 17 Sep 2006 19:08:24 -0400, "In Cognito" wrote:
>
> > Here's a way to heat up your cpu and crash the rest of the system too:
> >
> > main(){
> > asm("pushf\n"
> > "popl %eax\n"
> > /* enable the NT bit */
> > "orl $0x4000, %eax\n"
> > "pushl %eax\n"
> > "popf\n"
> >
> > "sysenter\n"
> > );
> > return 0;
> > }
>
> I'll take your word that it crashes.
It doesn't for me - I get a segfault.
That's on a PIII. Are recenter CPUs different in this regard?
> 2.6.9 is fine. I'd guess the iret fixups from 2.6.12 are the problem.
>
> This doesn't crash for me, but it's probably not quite the right fix:
>
> Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
> ---
> arch/i386/kernel/traps.c | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletion(-)
>
> --- 2.6.18-rc6-nb.orig/arch/i386/kernel/traps.c
> +++ 2.6.18-rc6-nb/arch/i386/kernel/traps.c
> @@ -516,6 +516,16 @@ fastcall void do_##name(struct pt_regs *
> do_trap(trapnr, signr, str, 0, regs, error_code, NULL); \
> }
>
> +#define DO_TSS_ERROR(trapnr, signr, str, name) \
> +fastcall void do_##name(struct pt_regs * regs, long error_code) \
> +{ \
> + if (notify_die(DIE_TRAP, str, regs, error_code, trapnr, signr) \
> + == NOTIFY_STOP) \
> + return; \
> + regs->eflags &= ~X86_EFLAGS_NT; \
> + do_trap(trapnr, signr, str, 0, regs, error_code, NULL); \
> +}
> +
> #define DO_ERROR_INFO(trapnr, signr, str, name, sicode, siaddr) \
> fastcall void do_##name(struct pt_regs * regs, long error_code) \
> { \
> @@ -561,7 +571,7 @@ DO_VM86_ERROR( 4, SIGSEGV, "overflow", o
> DO_VM86_ERROR( 5, SIGSEGV, "bounds", bounds)
> DO_ERROR_INFO( 6, SIGILL, "invalid opcode", invalid_op, ILL_ILLOPN, regs->eip)
> DO_ERROR( 9, SIGFPE, "coprocessor segment overrun", coprocessor_segment_overrun)
> -DO_ERROR(10, SIGSEGV, "invalid TSS", invalid_TSS)
> +DO_TSS_ERROR(10, SIGSEGV, "invalid TSS", invalid_TSS)
> DO_ERROR(11, SIGBUS, "segment not present", segment_not_present)
> DO_ERROR(12, SIGBUS, "stack segment", stack_segment)
> DO_ERROR_INFO(17, SIGBUS, "alignment check", alignment_check, BUS_ADRALN, 0)
> --
> Chuck
next prev parent reply other threads:[~2006-09-18 5:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 3:51 Chuck Ebbert
2006-09-18 5:25 ` Andrew Morton [this message]
2006-09-18 8:44 ` Mike Galbraith
2006-09-18 15:11 ` Linus Torvalds
2006-09-18 15:06 ` Ingo Molnar
2006-09-18 15:29 ` Andi Kleen
2006-09-18 15:24 ` Ingo Molnar
2006-09-18 16:02 ` Linus Torvalds
2006-09-18 16:10 ` Linus Torvalds
2006-09-18 16:24 ` Jeremy Fitzhardinge
2006-09-18 16:12 ` Benjamin LaHaise
2006-09-18 16:39 ` Andi Kleen
2006-09-18 19:01 ` Jeremy Fitzhardinge
[not found] <5a20704e0609171603s55ca52bap71dc2fa2c05d6741@mail.gmail.com>
2006-09-17 23:08 ` In Cognito
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=20060917222537.55241d19.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=76306.1226@compuserve.com \
--cc=defend.the.world@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®