From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Brian Gerst <brgerst@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, Stas Sergeev <stsp@list.ru>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH urgent 0/2] x86: vm86 fix and test
Date: Fri, 30 Oct 2015 22:42:44 -0700 [thread overview]
Message-ID: <cover.1446270067.git.luto@kernel.org> (raw)
Calling vm86 and then forking will corrupt things. Fix it.
This is for x86/urgent. It fixes a 4.3 regression.
Andy Lutomirski (2):
selftests/x86: Add a fork() to entry_from_vm86 to catch fork bugs
x86/vm86: Set thread.vm86 to NULL on fork/clone
arch/x86/kernel/process.c | 3 +++
tools/testing/selftests/x86/entry_from_vm86.c | 4 ++++
2 files changed, 7 insertions(+)
--
2.4.3
next reply other threads:[~2015-10-31 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 5:42 Andy Lutomirski [this message]
2015-10-31 5:42 ` [PATCH urgent 1/2] selftests/x86: Add a fork() to entry_from_vm86 to catch fork bugs Andy Lutomirski
2015-10-31 8:54 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2015-10-31 5:42 ` [PATCH urgent 2/2] x86/vm86: Set thread.vm86 to NULL on fork/clone Andy Lutomirski
2015-10-31 8:55 ` [tip:x86/urgent] " tip-bot for 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=cover.1446270067.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@list.ru \
--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).