From: Tejun Heo <tj@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] workqueue: avoid hard lockups in show_workqueue_state()
Date: Fri, 12 Jan 2018 11:40:47 -0800 [thread overview]
Message-ID: <20180112194047.GN3460072@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180111005335.24642-1-sergey.senozhatsky@gmail.com>
On Thu, Jan 11, 2018 at 09:53:35AM +0900, Sergey Senozhatsky wrote:
> show_workqueue_state() can print out a lot of messages while being in
> atomic context, e.g. sysrq-t -> show_workqueue_state(). If the console
> device is slow it may end up triggering NMI hard lockup watchdog.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Applied to wq/for-4.15-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2018-01-12 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 0:53 Sergey Senozhatsky
2018-01-12 19:40 ` Tejun Heo [this message]
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=20180112194047.GN3460072@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.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
Powered by JetHome