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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200911031358.nA3DwTHw008484@demeter.kernel.org>
Date:	Tue, 3 Nov 2009 13:58:29 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 #172 from Theodore Tso <tytso@....edu>  2009-11-03 13:58:25 ---
There's a lot more we need to understand --- including why we weren't seeing a
printk message indicating a journal checksum, and which commit was showing the
checksum failure, and why we ended up seeing a checksum failure in the first
place.   If it was the last commit that was being written right before the
system crash, the commit block simply should have been missing due to the
barrier.   But we can do this without having to worry about 2.6.32 being a QA
disaster for ext4.  :-)

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