From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <bp@alien8.de>, Oleg Nesterov <oleg@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Alexei Starovoitov <ast@plumgrid.com>,
Will Drewry <wad@chromium.org>, Kees Cook <keescook@chromium.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: entry_32.S: change ESPFIX test to not touch PT_OLDSS(%esp)
Date: Tue, 10 Mar 2015 07:25:46 +0100 [thread overview]
Message-ID: <20150310062545.GA16065@gmail.com> (raw)
In-Reply-To: <CALCETrVLSgayUzP4nrjXVjGwcFQ=Ue6OvQkKHRio_y8Y0oWLVA@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> On Mon, Mar 9, 2015 at 11:16 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Mon, Mar 9, 2015 at 11:04 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> >>
> >> One option would be to change the NMI entry code to move itself down 8
> >> bytes if this happens (came from kernel mode or sp == sp0 - 12,
> >> perhaps).
> >
> > Hmm. That whole code currently depends on the stack setup being just a
> > single instruction (the move to esp). And that simplifies things, I'd
> > like to keep it that way.
> >
> > I'd *much* rather just keep the 8-byte padding. What was so
> > problematic with that? It worked. It's been around forever. Removing
> > it is the bug.
>
> Let's at least fix it, then. processor.h has:
>
> #define INIT_TSS { \
> .x86_tss = { \
> .sp0 = sizeof(init_stack) + (long)&init_stack, \
>
> (moved in -tip)
>
> That's bogus, and this bogosity is why I broke 32-bit -next in the
> first place: I assumed it was correct.
>
> I'll get it if no one beats me to it.
Please do and please post patches ASAP so that I can move tip:x86/asm
back into a correct state again.
Thanks,
Ingo
prev parent reply other threads:[~2015-03-10 6:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 14:05 [PATCH] x86: entry_32.S: change ESPFIX test to not touch PT_OLDSS(%esp) Denys Vlasenko
2015-03-09 14:18 ` Andy Lutomirski
2015-03-09 15:00 ` Denys Vlasenko
2015-03-09 15:09 ` Andy Lutomirski
2015-03-09 19:31 ` Denys Vlasenko
2015-03-09 15:13 ` Ingo Molnar
2015-03-09 15:18 ` Andy Lutomirski
2015-03-09 15:47 ` Steven Rostedt
2015-03-09 15:54 ` Ingo Molnar
2015-03-09 16:08 ` Linus Torvalds
2015-03-09 16:28 ` Denys Vlasenko
2015-03-09 16:44 ` Linus Torvalds
2015-03-09 17:44 ` H. Peter Anvin
2015-03-09 19:13 ` Andy Lutomirski
2015-03-09 19:26 ` H. Peter Anvin
2015-03-09 19:51 ` Andy Lutomirski
2015-03-09 17:42 ` H. Peter Anvin
2015-03-09 17:45 ` Andy Lutomirski
2015-03-09 17:59 ` Linus Torvalds
2015-03-09 18:04 ` Andy Lutomirski
2015-03-09 18:16 ` Linus Torvalds
2015-03-09 18:32 ` Denys Vlasenko
2015-03-09 18:36 ` Andy Lutomirski
2015-03-10 6:25 ` Ingo Molnar [this message]
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=20150310062545.GA16065@gmail.com \
--to=mingo@kernel.org \
--cc=ast@plumgrid.com \
--cc=bp@alien8.de \
--cc=dvlasenk@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=wad@chromium.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.