From: Stas Sergeev <stsp@list.ru>
To: Andy Lutomirski <luto@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Stas Sergeev <stsp@users.sourceforge.net>
Subject: Re: [PATCH v2 0/4] x86: sigcontext fixes, again
Date: Mon, 26 Oct 2015 14:45:50 +0300 [thread overview]
Message-ID: <562E126E.6030300@list.ru> (raw)
In-Reply-To: <cover.1445822498.git.luto@kernel.org>
26.10.2015 04:25, Andy Lutomirski пишет:
> 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).
I'll test it myself then.
But this will have to wait till a week-end I am afraid.
In a mean time you can test vm86() - last time I tried,
I got oops and hard lockup.
> 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
No, another option is a new SA_ flag.
next prev parent reply other threads:[~2015-10-26 11:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 1:25 [PATCH v2 0/4] x86: sigcontext fixes, again Andy Lutomirski
2015-10-26 1:25 ` [PATCH v2 1/4] x86/signal/64: Add a comment about sigcontext->fs and gs Andy Lutomirski
2015-10-31 15:25 ` Stas Sergeev
2015-12-07 23:23 ` Andy Lutomirski
2015-12-29 12:24 ` Stas Sergeev
2015-12-29 12:31 ` Andy Lutomirski
2015-10-26 1:25 ` [PATCH v2 2/4] x86/signal/64: Fix SS if needed when delivering a 64-bit signal Andy Lutomirski
2015-10-26 1:25 ` [PATCH v2 3/4] x86/signal/64: Re-add support for SS in the 64-bit signal context Andy Lutomirski
2015-10-31 15:18 ` Stas Sergeev
2015-10-26 1:25 ` [PATCH v2 4/4] selftests/x86: Add tests for UC_SIGCONTEXT_SS and UC_STRICT_RESTORE_SS Andy Lutomirski
2015-10-26 11:45 ` Stas Sergeev [this message]
2015-10-27 0:52 ` [PATCH v2 0/4] x86: sigcontext fixes, again Andy Lutomirski
2015-10-27 14:05 ` Stas Sergeev
2015-10-27 22:37 ` Linus Torvalds
2015-10-28 0:04 ` Toshi Kani
2015-10-28 9:53 ` Stas Sergeev
2015-10-28 16:34 ` Toshi Kani
2015-10-28 19:22 ` Toshi Kani
2015-10-28 22:51 ` Toshi Kani
2015-10-31 11:58 ` Stas Sergeev
2015-11-02 17:01 ` Toshi Kani
2015-10-30 23:50 ` Andy Lutomirski
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=562E126E.6030300@list.ru \
--to=stsp@list.ru \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=stsp@users.sourceforge.net \
--cc=torvalds@linux-foundation.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 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).