From: "chengjian (D)" <cj.chengjian@huawei.com>
To: Petr Mladek <pmladek@suse.com>
Cc: <linux-kernel@vger.kernel.org>, <chenwandun@huawei.com>,
<xiexiuqi@huawei.com>, <bobo.shaobowang@huawei.com>,
<huawei.libin@huawei.com>, <sergey.senozhatsky@gmail.com>,
<rostedt@goodmis.org>, "chengjian (D)" <cj.chengjian@huawei.com>
Subject: Re: [RFC PATCH] panic: fix deadlock in panic()
Date: Fri, 5 Jun 2020 18:42:57 +0800 [thread overview]
Message-ID: <7b6f8522-f9b2-29e8-2dde-3bbfac19335b@huawei.com> (raw)
In-Reply-To: <20200604082947.GB22497@linux-b0ei>
Hi, Petr
On 2020/6/4 16:29, Petr Mladek wrote:
> It might cause double unlock (deadlock) on architectures that did not
> use NMI to stop the CPUs.
>
> I have created a conservative fix for this problem for SLES, see
> https://github.com/openSUSE/kernel-source/blob/SLE15-SP2-UPDATE/patches.suse/printk-panic-Avoid-deadlock-in-printk-after-stopping-CPUs-by-NMI.patch
> It solves the problem only on x86 architecture.
>
> There are many hacks that try to solve various scenarios but it
> is getting too complicated and does not solve all problems.
I have read your conservative fix and I have some question,
1-- does the console_sem need to be reinitialized ?
2-- Other architectures without NMI, is there no such problem ?
> The only real solution is lockless printk(). First piece is a lockless
> ringbuffer. See the last version at
> https://lore.kernel.org/r/20200501094010.17694-1-john.ogness@linutronix.de
>
> We prefer to work on the lockless solution instead of adding more
> complicated workarounds. This is why I even did not try to upstream
> the patch for SLES.
>
> In the meantime, you might also consider removing the offending
> message from the panic notifier if it is not really important.
>
> Best Regards,
> Petr
>
> .
Thank you.
Cheng Jian
next prev parent reply other threads:[~2020-06-05 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 14:19 Cheng Jian
2020-06-04 7:59 ` Sergey Senozhatsky
2020-06-04 8:29 ` Petr Mladek
2020-06-05 10:42 ` chengjian (D) [this message]
2020-06-05 11:36 ` Petr Mladek
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=7b6f8522-f9b2-29e8-2dde-3bbfac19335b@huawei.com \
--to=cj.chengjian@huawei.com \
--cc=bobo.shaobowang@huawei.com \
--cc=chenwandun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=xiexiuqi@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
all inboxes | Powered by JetHome®