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: <20071203072328.371d0b00@laptopd505.fenrus.org>
Date:	Mon, 3 Dec 2007 07:23:28 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Radoslaw Szkodzinski <lkml@...ralstorm.puszkin.org>,
	Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
	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

On Mon, 3 Dec 2007 11:27:15 +0100
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?  Or just the SCSI driver decides to do lengthy
> error recovery  -- you could argue that is broken if it takes longer 
> than 2 minutes, but in practice these things are hard to test
> and to fix.
> 

the scsi layer will have the IO totally aborted within that time anyway;
the retry timeout for disks is 30 seconds after all.




-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/