From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>,
linux-kernel@vger.kernel.org, Brian Gerst <brgerst@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>, Willy Tarreau <w@1wt.eu>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 1/3] x86/entry/64: Refactor IRQ stacks and make them NMI-safe
Date: Sun, 26 Jul 2015 08:05:43 +0200 [thread overview]
Message-ID: <20150726060543.GA18853@nazgul.tnic> (raw)
In-Reply-To: <13a3ceb8d36e5fa77b3b9e7a2006245a72b25f5d.1437803711.git.luto@kernel.org>
On Fri, Jul 24, 2015 at 10:57:04PM -0700, Andy Lutomirski wrote:
> This will allow IRQ stacks to nest inside NMIs or similar entries
> that can happen during IRQ stack setup or teardown.
>
> The Xen code here has a confusing comment.
>
> The new macros won't work correctly if they're invoked with IRQs on.
> Add a check under CONFIG_DEBUG_ENTRY to detect that.
>
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> ---
> arch/x86/Kconfig.debug | 2 -
> arch/x86/entry/entry_64.S | 89 +++++++++++++++++++++++++++++---------------
> arch/x86/kernel/process_64.c | 4 ++
> 3 files changed, 63 insertions(+), 32 deletions(-)
What does that apply against?
I get conflicts against current Linus master:
$ patch -p1 --dry-run -i /tmp/0001-x86-entry-64-refactor_irq_stacks_and_make_them_nmi-safe.patch
checking file arch/x86/Kconfig.debug
checking file arch/x86/entry/entry_64.S
Hunk #1 succeeded at 544 (offset 54 lines).
Hunk #2 FAILED at 568.
Hunk #3 FAILED at 598.
Hunk #4 succeeded at 1012 (offset 99 lines).
Hunk #5 succeeded at 1033 (offset 99 lines).
2 out of 5 hunks FAILED
checking file arch/x86/kernel/process_64.c
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-07-26 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 5:57 [PATCH v2 0/3] x86_64: Make int3 non-magical Andy Lutomirski
2015-07-25 5:57 ` [PATCH v2 1/3] x86/entry/64: Refactor IRQ stacks and make them NMI-safe Andy Lutomirski
2015-07-26 6:05 ` Borislav Petkov [this message]
2015-07-26 18:50 ` Andy Lutomirski
2015-07-28 9:41 ` Borislav Petkov
2015-08-17 11:18 ` Andy Shevchenko
2015-08-19 15:50 ` Andy Lutomirski
2015-07-25 5:57 ` [PATCH v2 2/3] x86/entry/64: Teach idtentry to use the IRQ stack Andy Lutomirski
2015-07-28 9:50 ` Borislav Petkov
2015-07-25 5:57 ` [PATCH v2 3/3] x86/entry/64: Move #BP from IST to " Andy Lutomirski
2015-07-28 9:54 ` Borislav Petkov
2015-07-29 17:57 ` Andy Lutomirski
2015-07-30 4:19 ` Borislav Petkov
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=20150726060543.GA18853@nazgul.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
--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
all inboxes | Powered by JetHome®