linux-kernel - Re: Hung task detector versus NFS (TASK

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: <20160308031119.GM23621@tassilo.jf.intel.com>
Date:	Mon, 7 Mar 2016 19:11:19 -0800
From:	Andi Kleen <ak@...ux.intel.com>
To:	Simon Kirby <sim@...tway.ca>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Hung task detector versus NFS (TASK_KILLABLE)

> I write this because I would actually find it useful to see the original
> backtrace, even if it is interruptible, not just the collateral damage.
> Since the "skipping" of NFS is basically incomplete anyway, how big a
> deal is this "feature"?

Random backtrace spewing is always a misfeature for 99.99+% of the users
for whom it is gibberish.

If you really need it yourself add a kprobe.

-Andi