From: Andy Lutomirski <luto@amacapital.net>
To: Borislav Petkov <bp@alien8.de>, x86@kernel.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 v2 0/2] Handle IST interrupts from userspace on the normal stack
Date: Thu, 13 Nov 2014 14:31:19 -0800 [thread overview]
Message-ID: <cover.1415917623.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.
Andy Lutomirski (2):
x86, entry: Switch stacks on a paranoid entry from userspace
uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME
Documentation/x86/entry_64.txt | 18 +++++---
Documentation/x86/x86_64/kernel-stacks | 8 ++--
arch/x86/include/asm/thread_info.h | 2 +-
arch/x86/kernel/entry_64.S | 82 +++++++++++++++++-----------------
arch/x86/kernel/traps.c | 23 +++-------
kernel/events/uprobes.c | 1 -
6 files changed, 65 insertions(+), 69 deletions(-)
--
1.9.3
next reply other threads:[~2014-11-13 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 22:31 Andy Lutomirski [this message]
2014-11-13 22:31 ` [PATCH v2 1/2] x86, entry: Switch stacks on a paranoid entry from userspace Andy Lutomirski
2014-11-13 22:31 ` [PATCH v2 2/2] uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME Andy Lutomirski
2014-11-14 6:08 ` Srikar Dronamraju
2014-11-14 7:01 ` Andy Lutomirski
2014-11-14 7:15 ` Srikar Dronamraju
2014-11-13 23:19 ` [PATCH v2 0/2] Handle IST interrupts from userspace on the normal stack 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.1415917623.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=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.