linux-kernel - Re: [Bug #13374] reiserfs blocked for more than 120secs

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] [day] [month] [year] [list]

Date:	Wed, 19 Aug 2009 10:54:36 +0900
From:	Tejun Heo <htejun@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Harald Dunkel <harald.dunkel@...nline.de>,
	Frédéric Weisbecker 
	<fweisbec@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Jeff Mahoney <jeffm@...e.com>
Subject: Re: [Bug #13374] reiserfs blocked for more than 120secs

Hello,

Rafael J. Wysocki wrote:
> Unfortunately, I don't have much experience with debugging issues of
> this kind.  Perhaps Tejun will have some hints (CC added)?

Eh... I don't have much experience either and from the reported
information I can't tell much.  The question would be what the thread
which is holding the lock was doing and whether it traces down to IO
layer.  So, as Jeff said, we'll need sysrq-t output to tell what's
going on.  The current trace only reveals the victim not the offender.

Thanks.

-- 
tejun
--
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/