On Wed, Jul 11, 2007 at 11:19:38PM -0600, Andreas Dilger wrote:
On Jul 11, 2007 17:20 +0200, Andi Kleen wrote:
If you use a normal pseudo random number generator and print the seed
(e.g. create from the time) initially the image can be easily recreated
later without shipping it around.
On Wed, Jul 11, 2007 at 03:44:11AM -0600, Andreas Dilger wrote:
I've already found some kind of memory corruption in e2fsck as a result
of running this as a regular user. It segfaults in qsort() when freeing
memory. The image that causes this problem is attached, and it happens
with the
On Jul 11, 2007 13:43 -0400, Theodore Tso wrote:
Fix e2fsck segfault on very badly damaged filesystems
--- a/e2fsck/dirinfo.c
+++ b/e2fsck/dirinfo.c
@@ -126,7 +126,7 @@ void e2fsck_add_dir_info(e2fsck_t ctx, ext2_ino_t ino,
ext2_ino_t parent)
ctx-dir_info-size +=
I've got another one, but it isn't a show stopper I think.
If you format a filesystem with both resize_inode and meta_bg you get an
unfixable filesystem. The bad news is that it appears that running
e2fsck on the filesystem is actually _causing_ the corruption in this case
(trying to rebuild the
-a $OUT
+ echo failed
+ echo *** This appears to be a bug in e2fsprogs ***
+ echo Please contact linux-ext4 for further assistance.
+ echo Include $OUT as an attachment, and save $ARCHIVE locally for future reference.
+ unset_vars
+ break;
+}
+
+echo -n Random corruption test for e2fsck:
+# Truncate
