From: Andy Lutomirski <luto@amacapital.net>
To: Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>, Tony Luck <tony.luck@intel.com>,
Andi Kleen <andi@firstfloor.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH v3 0/3] Handle IST interrupts from userspace on the normal stack
Date: Tue, 18 Nov 2014 15:15:16 -0800 [thread overview]
Message-ID: <cover.1416352397.git.luto@amacapital.net> (raw)
We currently run IST interrupt handlers on the IST stack. Changing
it may simplify a few things. See patch 2 for details.
Patch 1 is a fix for a not-quite-bug in uprobes that Oleg noticed
that would be exposed by patch 2.
NB: Tony has seen odd behavior when stress-testing injected
machine checks with this series applied. I suspect that
it's a bug in something else, possibly his BIOS. Bugs in
this series shouldn't be ruled out, though.
Andy Lutomirski (3):
uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME
x86, entry: Switch stacks on a paranoid entry from userspace
sched, x86: Check that we're on the right stack in schedule and
__might_sleep
Documentation/x86/entry_64.txt | 18 ++++---
Documentation/x86/x86_64/kernel-stacks | 8 ++--
arch/x86/Kconfig | 1 +
arch/x86/include/asm/thread_info.h | 19 +++++++-
arch/x86/kernel/entry_64.S | 86 ++++++++++++++++++----------------
arch/x86/kernel/irq_32.c | 13 ++---
arch/x86/kernel/traps.c | 23 ++-------
include/linux/thread_info.h | 7 +++
kernel/Kconfig.locks | 3 ++
kernel/events/uprobes.c | 1 -
kernel/sched/core.c | 14 ++++--
11 files changed, 109 insertions(+), 84 deletions(-)
--
1.9.3
next reply other threads:[~2014-11-18 23:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 23:15 Andy Lutomirski [this message]
2014-11-18 23:15 ` [PATCH v3 1/3] uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME Andy Lutomirski
2014-11-18 23:15 ` [PATCH v3 2/3] x86, entry: Switch stacks on a paranoid entry from userspace Andy Lutomirski
2014-11-18 23:15 ` [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep Andy Lutomirski
2014-11-19 18:40 ` Linus Torvalds
2014-11-19 19:23 ` Andy Lutomirski
2014-11-19 19:29 ` Andi Kleen
2014-11-19 19:44 ` Linus Torvalds
2014-11-19 23:04 ` Andy Lutomirski
2014-11-19 23:23 ` Linus Torvalds
2014-11-19 23:32 ` Thomas Gleixner
2014-11-19 23:42 ` Linus Torvalds
2014-11-19 23:49 ` Andy Lutomirski
2014-11-19 23:59 ` Linus Torvalds
2014-11-20 0:13 ` Andy Lutomirski
2014-11-20 0:37 ` Linus Torvalds
2014-11-20 0:46 ` Andy Lutomirski
2014-11-20 1:09 ` Linus Torvalds
2014-11-20 1:11 ` Andy Lutomirski
2014-11-20 10:28 ` Borislav Petkov
2014-11-20 23:25 ` Andy Lutomirski
2014-11-20 7:45 ` Ingo Molnar
2016-02-29 5:27 ` Andy Lutomirski
2016-05-24 1:23 ` Andy Lutomirski
2016-05-24 1:48 ` Linus Torvalds
2016-05-24 2:09 ` Andy Lutomirski
2016-05-24 2:16 ` Linus Torvalds
2014-11-19 18:29 ` [PATCH v3 0/3] Handle IST interrupts from userspace on the normal stack Luck, Tony
2014-11-19 22:15 ` [PATCH] x86, mce: Get rid of TIF_MCE_NOTIFY and associated mce tricks Luck, Tony
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.1416352397.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.com \
--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).