[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120817132237.GA311@localhost>
Date: Fri, 17 Aug 2012 21:22:37 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Theodore Ts'o <tytso@....edu>, Marti Raudsepp <marti@...fo.org>,
Kernel hackers <linux-kernel@...r.kernel.org>,
ext4 hackers <linux-ext4@...r.kernel.org>, maze@...gle.com
Subject: Re: NULL pointer dereference in ext4_ext_remove_space on 3.5.1
Hi Ted,
On Fri, Aug 17, 2012 at 09:15:58AM -0400, Theodore Ts'o wrote:
> Thanks Fengguang:
>
> For the record, I was able to find my own easy repro, last night using
> only a 220 meg partition:
>
> # mke2fs -t ext4 -b 1024 -J size=1 /dev/vdc
> # mount -t ext2 /dev/vdc /vdc
> # mkdir /vdc/a
> # cd /vdc/a
> # seq 1 210000 | xargs -n 1 fallocate -l 1m
> # seq 1 2 210000 | xargs /bin/rm
> # mkdir /vdc/b
> # cd /vdc/b
> # seq 1 103 | xargs -n 1 fallocate -l 1g
> # cd /
> # umount /vdc
> # mount -t ext4 -o commit=10000 /dev/vdc /vdc
> # rm -rf /vdc/b
It makes a nice and simple test script, I'd very like to add it to my
0day test system :-)
> For future reference, there are a couple of things that are of
> interest to ext4 developers when trying to create repro's:
>
> 1) The use of mounting with ext2 to speed up the setup.
>
> 2) The first two "seq ... | xargs ..." commands to create a very
> fragmented file system.
>
> 3) Using a 1k block size file system to stress the extent tree code
> and htree directory (since its easier to make larger tree structure).
>
> 4) The use of the mount option commit=10000 to test what happens when
> the journal is full (without using a nice, fast device such as RAID array
> or without burning write cycles on an expensive flash device.)
Thanks for the directions! I'll make that a big comment.
Thanks,
Fengguang
--
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