From: Xin Li <xin@zytor.com>
To: paulmck@kernel.org, Breno Leitao <leitao@debian.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
leit@meta.com, Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@kernel.org>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/nmi: Fix "in NMI handler" check
Date: Wed, 7 Feb 2024 10:44:57 -0800 [thread overview]
Message-ID: <0fabf792-3a9e-48c9-9f83-286905b5b2d3@zytor.com> (raw)
In-Reply-To: <c128c9b0-6bfa-4d62-9bc9-1215ee12ce2b@paulmck-laptop>
On 2/7/2024 10:30 AM, Paul E. McKenney wrote:
> On Wed, Feb 07, 2024 at 08:52:35AM -0800, Breno Leitao wrote:
>> Commit 344da544f177 ("x86/nmi: Print reasons why backtrace NMIs are
>> ignored") creates a super nice framework to diagnose NMIs.
>>
>> Every time nmi_exc() is called, it increments a per_cpu counter
>> (nsp->idt_nmi_seq). At its exit, it also increments the same counter.
>> Looking at this counter, you can see how many times that function was
>> called (dividing by 2), and, if the function is still being executed, by
>> checking the idt_nmi_seq's last bit.
>>
>> On the check side (nmi_backtrace_stall_check()), that variable is
>> queried to check if the NMI is still being executed, but, there is a
>> mistake in the bitwise operation. That code wants to check if the last
>> bit of the idt_nmi_seq is set or not, but, does the opposite, and check
>> for all the other bits, which will always be true after the first
>> exc_nmi() executed successfully.
>>
>> This appends the misleading string to the dump "(CPU currently in NMI
>> handler function)"
>>
>> Fix it by checking the last bit, and if it is set, append the string.
>>
>> Fixes: 344da544f177 ("x86/nmi: Print reasons why backtrace NMIs are ignored")
>> Signed-off-by: Breno Leitao <leitao@debian.org>
>
> If someone else is taking this:
>
> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
>
> (I am queueing it for testing in any case.)
Does this fix need to be backported?
Commit 344da544f177 has a date on Dec 16 2022.
>
>> ---
>> arch/x86/kernel/nmi.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c
>> index 17e955ab69fe..6e738ad474dc 100644
>> --- a/arch/x86/kernel/nmi.c
>> +++ b/arch/x86/kernel/nmi.c
>> @@ -639,7 +639,7 @@ void nmi_backtrace_stall_check(const struct cpumask *btp)
>> msgp = nmi_check_stall_msg[idx];
>> if (nsp->idt_ignored_snap != READ_ONCE(nsp->idt_ignored) && (idx & 0x1))
>> modp = ", but OK because ignore_nmis was set";
>> - if (nmi_seq & ~0x1)
>> + if (nmi_seq & 0x1)
>> msghp = " (CPU currently in NMI handler function)";
>> else if (nsp->idt_nmi_seq_snap + 1 == nmi_seq)
>> msghp = " (CPU exited one NMI handler function)";
>> --
>> 2.39.3
>>
>
--
Thanks!
Xin
next prev parent reply other threads:[~2024-02-07 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 16:52 Breno Leitao
2024-02-07 18:30 ` Paul E. McKenney
2024-02-07 18:44 ` Xin Li [this message]
2024-02-08 14:59 ` Breno Leitao
2024-02-26 22:50 ` [tip: x86/misc] x86/nmi: Fix the inverse " tip-bot2 for Breno Leitao
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=0fabf792-3a9e-48c9-9f83-286905b5b2d3@zytor.com \
--to=xin@zytor.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@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
all inboxes | Powered by JetHome®