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: <20071203103815.GA2707@elte.hu>
Date:	Mon, 3 Dec 2007 11:38:15 +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:

> > Kernel waiting 2 minutes on TASK_UNINTERRUPTIBLE is certainly broken.
> 
> What should it do when the NFS server doesn't answer anymore or when 
> the network to the SAN RAID array located a few hundred KM away 
> develops some hickup?  [...]

maybe: if the user does a Ctrl-C (or a kill -9), the kernel should try 
to honor it, instead of staying there stuck for a very long time 
(possibly forever)?

I think you are somehow confusing two issues: this patch in no way 
declares that "long waits are bad" - if the user _choses_ to wait for 
the NFS server (after phoning IT quickly or whatever), he can wait an 
hour. This patch only declares that "long waits _that the user has no 
way to stop_ are quite likely bad".

Do you see the important distinction between the two cases? Please 
reconsider your position (or re-state it differently), it just makes no 
rational sense to me so far.

	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/