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: <20071203143300.GA9518@elte.hu>
Date:	Mon, 3 Dec 2007 15:33:00 +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:

> > debugging feature can be disabled/enabled on a wide scale already:
> > 
> >  - in the .config
> > 
> >  - runtime, temporarily, via:
> > 
> >      echo 0 > /proc/sys/kernel/hung_task_timeout_secs
> 
> That won't address my concerns about already "breaking" (as in 
> frightening the user etc.) common error handling scenarios by default.

wow, now you again use big scary words like "breaking" and 
"frightening", with is a nice addition to the ticking timebomb 
metaphore.

Andi, sadly you are not listening AT ALL, you are repeating the same 
argument again and again that has been disputed and countered. Either 
come up with a new argument or please stop wasting everyone's time.

It is undisputable that for most users an unexplained hang is far more 
"frightening" than a hang followed by an explanation in the syslog. That 
is a _hard fact_, and if you cannot accept that it's really your 
cognitive problem not ours...

	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/