linux-ext4 - [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards

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: <200910120218.n9C2Ig49010735@demeter.kernel.org>
Date:	Mon, 12 Oct 2009 02:18:42 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards

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

--- Comment #18 from Theodore Tso <tytso@....edu>  2009-10-12 02:18:41 ---
Created an attachment (id=23353)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=23353)
jbd2 debugging patch

The jbd2-checksum-debugging patch adds two options which can be added to the
boot line.   The first, jbd2.xsum_debug=1, will print two additional kernel
messages when replaying a journal that will help debug checksums.   The second,
jbd2.ignore_xsum=1, will cause jbd2 to ignore any checksum errors.

If you can come up with a repeatable test case, it would be useful to apply
this patch and then add "jbd2.xsum_debug=1 jbd2.ignore_xsum=1" to the boot
line.   Then let me know (a) if the problem goes away when you add the boot
command-line options, and (b) give me the dmesg output either way.

Thanks!

-- 
Configure bugmail: http://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