linux-kernel - Re: getting uninterruptible sleep processes after upgrade from 2.6.20.20 to 2.6.24.2

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: <47C141B9.7050001@gmail.com>
Date:	Sun, 24 Feb 2008 11:06:49 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Stefan Priebe - allied internet ag <s.priebe@...ied-internet.ag>
CC:	Arjan van de Ven <arjan@...radead.org>,
	Christian Kujau <lists@...dbynature.de>,
	LKML <linux-kernel@...r.kernel.org>, xfs-masters@....sgi.com,
	xfs@....sgi.com, Al Viro <viro@...iv.linux.org.uk>,
	linux-fsdevel@...r.kernel.org
Subject: Re: getting uninterruptible sleep processes after upgrade from 2.6.20.20
 to 2.6.24.2

Ccing xfs team

On 02/21/2008 02:37 PM, Stefan Priebe - allied internet ag wrote:
> Hello!
> 
> I'm using XFS. dmesg -s32000 does not help - no more output. In messages 
> there is also no relevant output. Other than what I've posted here:
> http://lkml.org/lkml/2008/2/21/76

http://lkml.org/lkml/2008/2/21/86

Some kind of borkage in readdir, probably either in xfs or vfs?

> Sorry but i cannot recompile the kernel on all machines again - another 
> downtime is not possible at the moment.
> 
> Stefan
> 
> Jiri Slaby schrieb:
>> Stefan Priebe - allied internet ag napsal(a):
>>> Hello!
>>>
>>> I've done the (echo t > /proc/sysrq-trigger) now but i'm not able to get
>>> the whole output via dmesg.
>>>
>>> Here is what i get:
>>> # dmesg
>>> 3.432124]  [<c0165a11>] do_select+0x390/0x46e
>>> [272363.432226]  [<c0166107>] __pollwait+0x0/0xcf
>>> [272363.432319]  [<c0115d90>] default_wake_function+0x0/0x8
>>
>> dmesg ring buffer is too small to fit this in. Please repeat it once 
>> again
>> with bigger ringbuffer (dmesg -s if you have this chosen in your 
>> kernel) or
>> post /var/log/meassages output of all processes. I see only waiters in
>> readdir, not seeing who could block them.
>>
>> Which filesystem did you run du on?
--
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/