From: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: x86@kernel.org, Jonathan Corbet <corbet@lwn.net>,
Peter Zijlstra <peterz@infradead.org>,
linux-doc@vger.kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [V2 PATCH 1/3] x86/panic: Fix re-entrance problem due to panic on NMI
Date: Tue, 28 Jul 2015 11:02:11 +0900 [thread overview]
Message-ID: <55B6E2A3.8070004@hitachi.com> (raw)
In-Reply-To: <20150727143405.GF11317@dhcp22.suse.cz>
Hi,
Thanks for the review.
(2015/07/27 23:34), Michal Hocko wrote:
> On Mon 27-07-15 10:58:50, Hidehiro Kawai wrote:
> [...]
>> diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c
>> index d05bd2e..5b32d81 100644
>> --- a/arch/x86/kernel/nmi.c
>> +++ b/arch/x86/kernel/nmi.c
>> @@ -230,7 +230,8 @@ void unregister_nmi_handler(unsigned int type, const char *name)
>> }
>> #endif
>>
>> - if (panic_on_unrecovered_nmi)
>> + if (panic_on_unrecovered_nmi &&
>> + atomic_cmpxchg(&panicking_cpu, -1, raw_smp_processor_id()) == -1)
>> panic("NMI: Not continuing");
>
> Spreading the check to all NMI callers is quite ugly. Wouldn't it be
> better to introduce nmi_panic() which wouldn't be __noreturn unlike the
> regular panic.
Sure. I'll fix it.
> The check could be also relaxed a bit and nmi_panic would
> return only if the ongoing panic is the current cpu when we really have
> to return and allow the preempted panic to finish.
It's reasonable. I'll do that in the next version.
> Something like
[...]
> +void nmi_panic(const char *fmt, ...)
Since we can't directly pass variable arguments to a subroutine,
we have to use a macro or do like this:
void nmi_panic(const char *msg)
{
...
panic("%s", msg);
}
If there is no objection, I'm going to use a macro.
> +{
> + /*
> + * We have to back off if the NMI has preempted an ongoing panic and
> + * allow it to finish
> + */
> + if (atomic_read(&panic_cpu) == raw_smp_processor_id())
> + return;
> +
> + panic();
> +}
> +EXPORT_SYMBOL(nmi_panic);
>
> struct tnt {
> u8 bit;
>
--
Hidehiro Kawai
Hitachi, Ltd. Research & Development Group
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vivek Goyal <vgoyal@redhat.com>,
linux-doc@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [V2 PATCH 1/3] x86/panic: Fix re-entrance problem due to panic on NMI
Date: Tue, 28 Jul 2015 11:02:11 +0900 [thread overview]
Message-ID: <55B6E2A3.8070004@hitachi.com> (raw)
In-Reply-To: <20150727143405.GF11317@dhcp22.suse.cz>
Hi,
Thanks for the review.
(2015/07/27 23:34), Michal Hocko wrote:
> On Mon 27-07-15 10:58:50, Hidehiro Kawai wrote:
> [...]
>> diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c
>> index d05bd2e..5b32d81 100644
>> --- a/arch/x86/kernel/nmi.c
>> +++ b/arch/x86/kernel/nmi.c
>> @@ -230,7 +230,8 @@ void unregister_nmi_handler(unsigned int type, const char *name)
>> }
>> #endif
>>
>> - if (panic_on_unrecovered_nmi)
>> + if (panic_on_unrecovered_nmi &&
>> + atomic_cmpxchg(&panicking_cpu, -1, raw_smp_processor_id()) == -1)
>> panic("NMI: Not continuing");
>
> Spreading the check to all NMI callers is quite ugly. Wouldn't it be
> better to introduce nmi_panic() which wouldn't be __noreturn unlike the
> regular panic.
Sure. I'll fix it.
> The check could be also relaxed a bit and nmi_panic would
> return only if the ongoing panic is the current cpu when we really have
> to return and allow the preempted panic to finish.
It's reasonable. I'll do that in the next version.
> Something like
[...]
> +void nmi_panic(const char *fmt, ...)
Since we can't directly pass variable arguments to a subroutine,
we have to use a macro or do like this:
void nmi_panic(const char *msg)
{
...
panic("%s", msg);
}
If there is no objection, I'm going to use a macro.
> +{
> + /*
> + * We have to back off if the NMI has preempted an ongoing panic and
> + * allow it to finish
> + */
> + if (atomic_read(&panic_cpu) == raw_smp_processor_id())
> + return;
> +
> + panic();
> +}
> +EXPORT_SYMBOL(nmi_panic);
>
> struct tnt {
> u8 bit;
>
--
Hidehiro Kawai
Hitachi, Ltd. Research & Development Group
next prev parent reply other threads:[~2015-07-28 2:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 1:58 [V2 PATCH 0/3] x86: Fix panic vs. NMI issues Hidehiro Kawai
2015-07-27 1:58 ` Hidehiro Kawai
2015-07-27 1:58 ` [V2 PATCH 3/3] x86/apic: Introduce noextnmi boot option Hidehiro Kawai
2015-07-27 1:58 ` Hidehiro Kawai
2015-07-27 1:58 ` [V2 PATCH 1/3] x86/panic: Fix re-entrance problem due to panic on NMI Hidehiro Kawai
2015-07-27 1:58 ` Hidehiro Kawai
2015-07-27 14:34 ` Michal Hocko
2015-07-27 14:34 ` Michal Hocko
2015-07-28 2:02 ` Hidehiro Kawai [this message]
2015-07-28 2:02 ` Hidehiro Kawai
2015-07-28 8:01 ` Michal Hocko
2015-07-28 8:01 ` Michal Hocko
2015-07-29 5:48 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-29 5:48 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-29 8:23 ` Michal Hocko
2015-07-29 8:23 ` Michal Hocko
2015-07-29 9:09 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-29 9:09 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-29 9:21 ` Michal Hocko
2015-07-29 9:21 ` Michal Hocko
2015-07-30 1:45 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 1:45 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 7:33 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 7:33 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 7:55 ` Michal Hocko
2015-07-30 7:55 ` Michal Hocko
2015-07-30 8:06 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 8:06 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 7:48 ` Michal Hocko
2015-07-30 7:48 ` Michal Hocko
2015-07-30 11:55 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 11:55 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-30 12:27 ` Michal Hocko
2015-07-30 12:27 ` Michal Hocko
2015-07-31 11:23 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-31 11:23 ` 河合英宏 / KAWAI,HIDEHIRO
2015-08-04 8:56 ` Michal Hocko
2015-08-04 8:56 ` Michal Hocko
2015-08-04 11:53 ` 河合英宏 / KAWAI,HIDEHIRO
2015-08-04 11:53 ` 河合英宏 / KAWAI,HIDEHIRO
2015-07-27 1:58 ` [V2 PATCH 2/3] kexec: Fix race between panic() and crash_kexec() called directly Hidehiro Kawai
2015-07-27 1:58 ` Hidehiro Kawai
2015-07-27 14:55 ` Michal Hocko
2015-07-27 14:55 ` Michal Hocko
2015-07-28 2:15 ` Hidehiro Kawai
2015-07-28 2:15 ` Hidehiro Kawai
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=55B6E2A3.8070004@hitachi.com \
--to=hidehiro.kawai.ez@hitachi.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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.