| 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
| ||
|
Message-Id: <200910272031.n9RKVTA4012312@demeter.kernel.org> Date: Tue, 27 Oct 2009 20:31: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 #132 from Eric Sandeen <sandeen@...hat.com> 2009-10-27 20:31:28 --- A few other observations from testing today. I'm driving a test on a lab box by doing a make modules_install into /tmp/modules on the victim box, and cycling power at some random point while that runs. 2.6.32 seems to hit this reliably, with the root fs pretty well munged. 2.6.31 hasn't seen it hit yet in my testing, maybe Linus' ext4_write_inode vs. writeback theory is correct ... Perhaps more strange, doing the same test on a non-root fs under 2.6.32 also doesn't seem to hit it reliably. Could it be something about the remount,ro flush of the root fs on the way down? Suspecting that possibly "mount -o ro; e2fsck -a /dev/root" during bootup was causing problems by writing to the mounted fs, I short-circuited the boot-time fsck -a; things were still badly corrupted so that doesn't seem to be it. -- 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