| 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
| ||
|
Date: Thu, 22 Oct 2009 18:43:47 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 #101 from Eric Sandeen <sandeen@...hat.com> 2009-10-22 18:43:36 --- (In reply to comment #87) > (In reply to comment #84) > > Maybe this is a totally stupid suggestion, but is there any chance for this > code path to be executed during journal replay, when s_journal is still NULL ? If I'm understanding Alexy's test correctly, he's not even doing journal replay; he's doing IO, crashing, and then running e2fsck -f -y immediately upon reboot w/o any fileystem mount (and therefore no journal replay) Alexy, is that correct? -- 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
Powered by blists - more mailing lists