| 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: <200910151507.n9FF7lqT005812@demeter.kernel.org> Date: Thu, 15 Oct 2009 15:07: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 #54 from Brian Rogers <brian@...w.org> 2009-10-15 15:07:41 --- A few times recently I had corruption very similar to what's reported here, with Ext4 on an ordinary disk partition with no DM or anything fancy. Personally I'm suspicious of the new boot scripts in Karmic. In trying to be as concurrent as possible, maybe it's doing something really bad like running twice and starting two concurrent instances of fsck on the same partition, or running fsck while the partition is already mounted with write access. I can confirm an issue where it doesn't reboot after directing you to manually run a disk check and instead it tries to remount the root partition as rw, reported here: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/452196 But that doesn't explain the disk getting corrupted in the first place. -- 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