From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>
Subject: Re: [tip: x86/entry] x86/entry: Treat BUG/WARN as NMI-like entries
Date: Mon, 15 Jun 2020 16:50:18 +0200 [thread overview]
Message-ID: <20200615145018.GU2531@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <159199140855.16989.18012912492179715507.tip-bot2@tip-bot2>
On Fri, Jun 12, 2020 at 07:50:08PM -0000, tip-bot2 for Andy Lutomirski wrote:
> +DEFINE_IDTENTRY_RAW(exc_invalid_op)
> {
> + bool rcu_exit;
> +
> + /*
> + * Handle BUG/WARN like NMIs instead of like normal idtentries:
> + * if we bugged/warned in a bad RCU context, for example, the last
> + * thing we want is to BUG/WARN again in the idtentry code, ad
> + * infinitum.
> + */
> + if (!user_mode(regs) && is_valid_bugaddr(regs->ip)) {
vmlinux.o: warning: objtool: exc_invalid_op()+0x47: call to probe_kernel_read() leaves .noinstr.text section
> + enum bug_trap_type type;
> +
> + nmi_enter();
> + instrumentation_begin();
> + trace_hardirqs_off_finish();
> + type = report_bug(regs->ip, regs);
> + if (regs->flags & X86_EFLAGS_IF)
> + trace_hardirqs_on_prepare();
> + instrumentation_end();
> + nmi_exit();
> +
> + if (type == BUG_TRAP_TYPE_WARN) {
> + /* Skip the ud2. */
> + regs->ip += LEN_UD2;
> + return;
> + }
> +
> + /*
> + * Else, if this was a BUG and report_bug returns or if this
> + * was just a normal #UD, we want to continue onward and
> + * crash.
> + */
> + }
> +
> + rcu_exit = idtentry_enter_cond_rcu(regs);
> + instrumentation_begin();
> handle_invalid_op(regs);
> + instrumentation_end();
> + idtentry_exit_cond_rcu(regs, rcu_exit);
> }
For now something like so will do, but we need a DEFINE_IDTENTRY_foo()
for the whole:
if (user_mode()) {
rcu = idtentry_enter_cond_rcu()
foo_user()
idtentry_exit_cond_rcu(rcu);
} else {
nmi_enter();
foo_kernel()
nmi_exit()
}
thing, we're repeating that far too often.
---
diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
index af75109485c26..a47e74923c4c8 100644
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -218,21 +218,22 @@ static inline void handle_invalid_op(struct pt_regs *regs)
DEFINE_IDTENTRY_RAW(exc_invalid_op)
{
- bool rcu_exit;
-
/*
* Handle BUG/WARN like NMIs instead of like normal idtentries:
* if we bugged/warned in a bad RCU context, for example, the last
* thing we want is to BUG/WARN again in the idtentry code, ad
* infinitum.
*/
- if (!user_mode(regs) && is_valid_bugaddr(regs->ip)) {
- enum bug_trap_type type;
+ if (!user_mode(regs)) {
+ enum bug_trap_type type = BUG_TRAP_TYPE_NONE;
nmi_enter();
instrumentation_begin();
trace_hardirqs_off_finish();
- type = report_bug(regs->ip, regs);
+
+ if (is_valid_bugaddr(regs->ip))
+ type = report_bug(regs->ip, regs);
+
if (regs->flags & X86_EFLAGS_IF)
trace_hardirqs_on_prepare();
instrumentation_end();
@@ -249,13 +250,16 @@ DEFINE_IDTENTRY_RAW(exc_invalid_op)
* was just a normal #UD, we want to continue onward and
* crash.
*/
- }
+ handle_invalid_op(regs);
+ } else {
+ bool rcu_exit;
- rcu_exit = idtentry_enter_cond_rcu(regs);
- instrumentation_begin();
- handle_invalid_op(regs);
- instrumentation_end();
- idtentry_exit_cond_rcu(regs, rcu_exit);
+ rcu_exit = idtentry_enter_cond_rcu(regs);
+ instrumentation_begin();
+ handle_invalid_op(regs);
+ instrumentation_end();
+ idtentry_exit_cond_rcu(regs, rcu_exit);
+ }
}
DEFINE_IDTENTRY(exc_coproc_segment_overrun)
next prev parent reply other threads:[~2020-06-15 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 3:26 [PATCH] x86/entry: Treat BUG/WARN as NMI-like entries Andy Lutomirski
2020-06-12 4:13 ` Andy Lutomirski
2020-06-12 19:50 ` [tip: x86/entry] " tip-bot2 for Andy Lutomirski
2020-06-15 14:50 ` Peter Zijlstra [this message]
2020-06-15 17:06 ` Andy Lutomirski
2020-06-15 19:44 ` Peter Zijlstra
2020-06-15 21:08 ` Andy Lutomirski
2020-06-15 22:23 ` Peter Zijlstra
2020-06-15 22:46 ` Andy Lutomirski
2020-06-16 11:14 ` Peter Zijlstra
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=20200615145018.GU2531@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--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