From: Richard Weinberger <richard@nod.at>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-um <linux-um@lists.infradead.org>,
kexec@lists.infradead.org, bhe@redhat.com,
Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-hyperv@vger.kernel.org, netdev <netdev@vger.kernel.org>,
x86 <x86@kernel.org>,
kernel-dev@igalia.com, kernel@gpiccoli.net, halves@canonical.com,
fabiomirmar@gmail.com,
alejandro j jimenez <alejandro.j.jimenez@oracle.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>, bp <bp@alien8.de>,
Jonathan Corbet <corbet@lwn.net>,
d hatayama <d.hatayama@jp.fujitsu.com>,
dave hansen <dave.hansen@linux.intel.com>,
dyoung@redhat.com, feng tang <feng.tang@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
mikelley@microsoft.com,
hidehiro kawai ez <hidehiro.kawai.ez@hitachi.com>,
jgross@suse.com, John Ogness <john.ogness@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@kernel.org>,
mhiramat@kernel.org, mingo <mingo@redhat.com>,
paulmck@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
senozhatsky@chromium.org, stern@rowland.harvard.edu,
tglx <tglx@linutronix.de>,
vgoyal@redhat.com, vkuznets@redhat.com, will@kernel.org,
xuqiang36@huawei.com,
anton ivanov <anton.ivanov@cambridgegreys.com>
Subject: Re: [PATCH V3 04/11] um: Improve panic notifiers consistency and ordering
Date: Sun, 18 Sep 2022 23:19:41 +0200 (CEST) [thread overview]
Message-ID: <2087154222.237106.1663535981252.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <1f464f3d-6668-9e05-bcb7-1b419b5373e1@igalia.com>
----- Ursprüngliche Mail -----
> Von: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
> On 19/08/2022 19:17, Guilherme G. Piccoli wrote:
>> Currently the panic notifiers from user mode linux don't follow
>> the convention for most of the other notifiers present in the
>> kernel (indentation, priority setting, numeric return).
>> More important, the priorities could be improved, since it's a
>> special case (userspace), hence we could run the notifiers earlier;
>> user mode linux shouldn't care much with other panic notifiers but
>> the ordering among the mconsole and arch notifier is important,
>> given that the arch one effectively triggers a core dump.
>>
>> Fix that by running the mconsole notifier as the first panic
>> notifier, followed by the architecture one (that coredumps).
>>
>> Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
>> Cc: Johannes Berg <johannes@sipsolutions.net>
>> Cc: Richard Weinberger <richard@nod.at>
>> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
>>
>> V3:
>> - No changes.
>> [...]
>
> Hi Johannes, sorry for the ping. Do you think you could pick this one?
> Or if you prefer, I can resend it alone (not in the series) - let me
> know your preference.
This patch is on my TODO list.
Just had no chance to test it.
Thanks,
//richard
next prev parent reply other threads:[~2022-09-18 21:19 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 22:17 [PATCH V3 00/11] The panic notifiers refactor - fixes/clean-ups (V3) Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 01/11] ARM: Disable FIQs (but not IRQs) on CPUs shutdown paths Guilherme G. Piccoli
2022-09-18 13:58 ` Guilherme G. Piccoli
2022-10-17 14:00 ` Guilherme G. Piccoli
2022-10-17 14:17 ` Russell King (Oracle)
2022-10-17 14:50 ` Guilherme G. Piccoli
2022-10-17 17:47 ` Russell King (Oracle)
2022-10-17 19:43 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 02/11] notifier: Add panic notifiers info and purge trailing whitespaces Guilherme G. Piccoli
2022-11-22 13:19 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 03/11] alpha: Clean-up the panic notifier code Guilherme G. Piccoli
2022-11-22 13:22 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 04/11] um: Improve panic notifiers consistency and ordering Guilherme G. Piccoli
2022-09-18 14:00 ` Guilherme G. Piccoli
2022-09-18 21:19 ` Richard Weinberger [this message]
2022-09-19 11:44 ` Guilherme G. Piccoli
2022-10-17 14:01 ` Guilherme G. Piccoli
2022-10-17 14:10 ` Richard Weinberger
2022-10-17 14:22 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 05/11] parisc: Replace regular spinlock with spin_trylock on panic path Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 06/11] tracing: Improve panic/die notifiers Guilherme G. Piccoli
2022-09-18 14:04 ` Guilherme G. Piccoli
2022-10-17 14:02 ` Guilherme G. Piccoli
2022-10-20 21:29 ` Steven Rostedt
2022-10-20 21:53 ` Guilherme G. Piccoli
2022-10-20 22:22 ` Steven Rostedt
2022-10-20 22:37 ` Guilherme G. Piccoli
2022-11-22 13:27 ` Guilherme G. Piccoli
2022-12-13 23:51 ` Guilherme G. Piccoli
2022-12-14 0:06 ` Steven Rostedt
2022-12-14 0:52 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 07/11] notifiers: Add tracepoints to the notifiers infrastructure Guilherme G. Piccoli
2022-09-18 14:07 ` Guilherme G. Piccoli
2022-10-17 14:04 ` Guilherme G. Piccoli
2022-11-22 13:30 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 08/11] EDAC/altera: Skip the panic notifier if kdump is loaded Guilherme G. Piccoli
2022-09-18 14:10 ` Guilherme G. Piccoli
2022-10-17 14:05 ` Guilherme G. Piccoli
2022-11-22 13:33 ` Guilherme G. Piccoli
2022-11-22 15:06 ` Borislav Petkov
2023-02-10 16:01 ` Guilherme G. Piccoli
2022-12-09 16:03 ` Petr Mladek
2022-08-19 22:17 ` [PATCH V3 09/11] video/hyperv_fb: Avoid taking busy spinlock on panic path Guilherme G. Piccoli
2022-09-18 14:12 ` Guilherme G. Piccoli
2022-10-04 16:17 ` Michael Kelley (LINUX)
2022-08-19 22:17 ` [PATCH V3 10/11] drivers/hv/vmbus, video/hyperv_fb: Untangle and refactor Hyper-V panic notifiers Guilherme G. Piccoli
2022-10-04 16:24 ` Michael Kelley (LINUX)
2022-10-04 17:20 ` Guilherme G. Piccoli
2022-10-17 15:26 ` Michael Kelley (LINUX)
2022-11-10 21:32 ` Guilherme G. Piccoli
2022-11-11 22:47 ` Wei Liu
2022-11-11 23:16 ` Wei Liu
2022-11-12 21:53 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 11/11] panic: Fixes the panic_print NMI backtrace setting Guilherme G. Piccoli
2022-09-18 14:13 ` Guilherme G. Piccoli
2022-11-22 13:35 ` Guilherme G. Piccoli
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=2087154222.237106.1663535981252.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=alejandro.j.jimenez@oracle.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=d.hatayama@jp.fujitsu.com \
--cc=dave.hansen@linux.intel.com \
--cc=dyoung@redhat.com \
--cc=fabiomirmar@gmail.com \
--cc=feng.tang@intel.com \
--cc=gpiccoli@igalia.com \
--cc=gregkh@linuxfoundation.org \
--cc=halves@canonical.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jgross@suse.com \
--cc=johannes@sipsolutions.net \
--cc=john.ogness@linutronix.de \
--cc=keescook@chromium.org \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=kexec@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=vkuznets@redhat.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xuqiang36@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).