From: Peter Zijlstra <peterz@infradead.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: mingo@kernel.org, akpm@linux-foundation.org, dvyukov@google.com,
paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, msb@chromium.org,
tglx@linutronix.de, vegard.nossum@oracle.com
Subject: Re: [PATCH v2] locking/hung_task: Show all hung tasks before panic
Date: Sat, 7 Apr 2018 17:39:37 +0200 [thread overview]
Message-ID: <20180407153937.GR4082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <201804072131.AEF86988.OFOQLJMVFFtOSH@I-love.SAKURA.ne.jp>
On Sat, Apr 07, 2018 at 09:31:19PM +0900, Tetsuo Handa wrote:
> are for replacing debug_show_all_locks() in check_hung_task() for cases like
> https://syzkaller.appspot.com/bug?id=26aa22915f5e3b7ca2cfca76a939f12c25d624db
> because we are interested in only threads holding locks.
>
> SysRq-t is too much but SysRq-w is useless for killable/interruptible threads...
Or use a script to process the sysrq-t output? I mean, we can add all
sorts, but where does it end?
next prev parent reply other threads:[~2018-04-07 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 14:12 [PATCH] locking/hung_task: Show all hung tasks before panic Tetsuo Handa
2018-04-02 15:35 ` Paul E. McKenney
2018-04-02 21:09 ` Tetsuo Handa
2018-04-03 15:23 ` Dmitry Vyukov
2018-04-04 22:05 ` [PATCH v2] " Tetsuo Handa
2018-04-07 12:31 ` Tetsuo Handa
2018-04-07 15:39 ` Peter Zijlstra [this message]
2018-04-07 16:03 ` Dmitry Vyukov
2018-04-07 16:24 ` Tetsuo Handa
2018-04-09 9:03 ` Dmitry Vyukov
2018-04-09 11:13 ` Tetsuo Handa
2018-04-09 11:50 ` Dmitry Vyukov
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=20180407153937.GR4082@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=msb@chromium.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.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