From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, Denys Vlasenko <dvlasenk@redhat.com>,
Stas Sergeev <stsp@list.ru>, Cyrill Gorcunov <gorcunov@gmail.com>,
Pavel Emelyanov <xemul@parallels.com>,
Brian Gerst <brgerst@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v4 0/4] x86: sigcontext fixes, again
Date: Tue, 16 Feb 2016 11:23:28 +0100 [thread overview]
Message-ID: <20160216102328.GB3902@pd.tnic> (raw)
In-Reply-To: <cover.1455589976.git.luto@kernel.org>
On Mon, Feb 15, 2016 at 06:38:12PM -0800, Andy Lutomirski wrote:
> This is take 2 at fixing x86 64-bit signals wrt SS. After a lot of
> thought, this is not controlled by any flags -- I would much prefer
> to avoid opt-in behavior. Instead, it just tries hard to avoid
> triggering the cases that break DOSEMU.
>
> Stas, this now seems to pass the test you sent me. It works with
> stock dosemu2 (I haven't tested classic dosemu because I can't get it
> to work regardless). It also works with a patched dosemu2 that bypasses
> the userspace trampoline:
>
> https://github.com/amluto/dosemu2/commit/571b4d08dc885b7a133e444a2ad23e0d21366206
>
> With this applied, all of the x86 selftests pass on x86_64. That
> wasn't the case before -- ldt_gdt_64 was broken.
>
> This is a bit risky, and another option would be to do nothing at
> all. Then we'd disable the problematic self-tests (sigh), and
> DOSEMU and similar tools will be stuck using gross hacks even on new
> kernels.
>
> Changes from v3:
> - Comment fixes from Borislav.
> - Improve AR_xyz comments to better match SDM. (Borislav, is this good?)
Yep, nice.
Thanks!
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2016-02-16 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 2:38 Andy Lutomirski
2016-02-16 2:38 ` [PATCH v4 1/4] x86/signal/64: Add a comment about sigcontext->fs and gs Andy Lutomirski
2016-02-16 7:42 ` Ingo Molnar
2016-02-16 14:50 ` Andy Lutomirski
2016-02-16 2:38 ` [PATCH v4 2/4] x86/signal/64: Fix SS if needed when delivering a 64-bit signal Andy Lutomirski
2016-02-16 2:38 ` [PATCH v4 3/4] x86/signal/64: Re-add support for SS in the 64-bit signal context Andy Lutomirski
2016-02-16 2:38 ` [PATCH v4 4/4] selftests/x86: Add tests for UC_SIGCONTEXT_SS and UC_STRICT_RESTORE_SS Andy Lutomirski
2016-02-16 10:23 ` Borislav Petkov [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=20160216102328.GB3902@pd.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=stsp@list.ru \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xemul@parallels.com \
/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®