| 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: Wed, 14 Oct 2009 03:17:22 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 #44 from Holger Freyther <zecke@...fish.org> 2009-10-14 03:17:21 --- (In reply to comment #43) > Hmm.... what were you doing right before the crash? It looks like you were > doing a kernel compile in /home/ich/source/linux/linux-2.6, since there were > files with a modtime of Tue Oct 13 16:25:55 2009. What's a funny is that > when these files were allocated, they used blocks that were apparently already > in use by other object files in that some source directory with a mod-time of > Sat Oct 10 13:51:14 2009. Did you do a "make clean" at any time between > Saturday and Tuesday that should have deleted these files? Not a make clean but a "rm -rf *; git checkout ." after the previous corruption in the source/linux/linux-2.6 directory. Is it feasible to come up with a self test patch to ext4 to compare the allocated block bitmap with the bitmap in memory? I will do a fsck on every boot now and will setup a testsystem in the evening to try to reproduce this (without dm/lvm inbetween). -- 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