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: <200910210053.n9L0r3en009274@demeter.kernel.org>
Date:	Wed, 21 Oct 2009 00:53:03 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 #96 from Theodore Tso <tytso@....edu>  2009-10-21 00:52:57 ---
Alexey, what version of GCC are you using?   If applying the patch in
attachment #23468 stops file system corruption, but you're not seeing the
message or the kernel stack dump that would be triggered by WARN_ON(1) in your
logs, then the conditional is never triggering.   So the only thing that might
be making a difference is if this is either moving some code around or some
kind of compiler bug.   Something really doesn't make sense, and there is
definitely something very subtle going on here.

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