linux-ext4 - [Bug 43292] jdb2 lockup with ext3 and nfs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120530133330.0407811FD1B@bugzilla.kernel.org>
Date:	Wed, 30 May 2012 13:33:30 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 43292] jdb2 lockup with ext3 and nfs

https://bugzilla.kernel.org/show_bug.cgi?id=43292





--- Comment #8 from Jan Kara <jack@...e.cz>  2012-05-30 13:33:29 ---
Hum, it looks exactly the same like the previous attempt. I'm starting to
suspect some problem with plugging or bio list handling. Since I can see you
can trigger the lockup pretty quickly, can you gather blktrace data for me? The
filesystem is on some device mapper device so you'll need to run something
like:
blktrace -d /dev/dm-2 -d /dev/sd? ...
where you include all scsi disks compounding the dm device. And then just
tar.gz the created files after the lockup happens and attach them here.
Hopefully we'll be able to see where the read got stuck. Thanks!

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html