linux-kernel - Re: [feature] automatically detect hung 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: <20071203130003.GA26372@elte.hu>
Date:	Mon, 3 Dec 2007 14:00:03 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Radoslaw Szkodzinski <lkml@...ralstorm.puszkin.org>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [feature] automatically detect hung TASK_UNINTERRUPTIBLE tasks

* Andi Kleen <andi@...stfloor.org> wrote:

> > you are over-designing it way too much - a backtrace is obviously 
> > very helpful and it must be printed by default. There's enough 
> > configurability in it already so that you can turn it off if you 
> > want.
> 
> So it will hit everybody first before they can figure out how to get 
> rid of it? That was the part I was objecting too.

you are apparently arguing in a circle. This is a debug mechanism. It 
goes the normal upstream acceptance process. I have booted this patch a 
few hundred times on a number of boxes and got not a single false 
positive so far. While this is in no way an exhaustive test, only more 
testing (in -mm, etc.) will tell us more, one way or another. Your 
negative feedback about an impending catastrophy has been duly noted 
(which vision of yours has not been shared by anyone else in this thread 
so far), and is given its due weight. Can we now please move on to a 
more productive stage?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/