linux-kernel - Re: [PATCH v2] locking/hung_task: Show all hung tasks before panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180407153937.GR4082@hirez.programming.kicks-ass.net>
Date:   Sat, 7 Apr 2018 17:39:37 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:     mingo@...nel.org, akpm@...ux-foundation.org, dvyukov@...gle.com,
        paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
        torvalds@...ux-foundation.org, msb@...omium.org,
        tglx@...utronix.de, vegard.nossum@...cle.com
Subject: Re: [PATCH v2] locking/hung_task: Show all hung tasks before panic

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?