linux-ext4 - [Bug 12885] kernel BUG at fs/jbd/transaction.c:1376!

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: <20090318191320.6CD11108040@picon.linux-foundation.org>
Date:	Wed, 18 Mar 2009 12:13:20 -0700 (PDT)
From:	bugme-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 12885] kernel BUG at fs/jbd/transaction.c:1376!

http://bugzilla.kernel.org/show_bug.cgi?id=12885

------- Comment #14 from tytso@....edu  2009-03-18 12:13 -------
In answer to your question in comment #12, yes, it's expected that processes
accessing the problematic directory might hang after a reboot, since when the
process died after the BUG, it probably left some locks locked, and so
processes would end up waiting forever for the locks to get unlocked (which
they won't since the process that held them died after the OOPS message).

But if this was caused by the unrar, then this might be harder to replicate....

In any case, if you haven't rebooted yet, I would try rebooting, and then
running e2fsck on the filesystem to make sure it is consistent.  Then the next
trick is to see what is needed to replicate the BUG/oops message.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
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