From: Dmitry Vyukov <dvyukov@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mandeep Singh Baines <msb@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH v2] locking/hung_task: Show all hung tasks before panic
Date: Sat, 7 Apr 2018 18:03:09 +0200 [thread overview]
Message-ID: <CACT4Y+Z6_P9mj2TEE3mtCez1je7dbviftM0rPcgsmQ-yFYYmBg@mail.gmail.com> (raw)
In-Reply-To: <20180407153937.GR4082@hirez.programming.kicks-ass.net>
On Sat, Apr 7, 2018 at 5:39 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> 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?
Good question.
We are talking about few dozen more stacks, right?
Not all kernel bugs are well reproducible, so it's not always possible
to go back and hit sysrq-t. And this come up in the context of syzbot,
which is an automated system. It reported a bunch of hangs and most of
them are real bugs, but not all of them are easily actionable.
Can it be a config or a command line argument, which will make syzbot
capture more useful context for each such hang?
next prev parent reply other threads:[~2018-04-07 16:03 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
2018-04-07 16:03 ` Dmitry Vyukov [this message]
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=CACT4Y+Z6_P9mj2TEE3mtCez1je7dbviftM0rPcgsmQ-yFYYmBg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--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=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).