From: Mingming Cao <cmm@us.ibm.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [PATCH] ext4: fix uniniatilized extend splitting error.
Date: Thu, 10 Jan 2008 15:42:55 -0800 [thread overview]
Message-ID: <1200008575.4012.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20080110143142.GC8685@dmon-lap.sw.ru>
Thanks for catching this, I added your fix to the ext4 patch queue
http://repo.or.cz/w/ext4-patch-queue.git
On Thu, 2008-01-10 at 17:31 +0300, Dmitry Monakhov wrote:
> Hi,
> While playing with new fancy fallocate interface on ext4 i've triggered
> bug which corrupted my grub :).
>
> My testcase:
> ~~~~~~~~~~~~
> blksize = 0x1000;
> fd = open(argv[1], O_RDWR|O_CREAT, 0700);
> unsigned long long sz = 0x10000000UL;
> /* allocating big blocks chunk */
> syscall(__NR_fallocate, fd, 0, 0UL, sz)
>
> /* grab all other available filesystem space */
> tfd = open("tmp", O_RDWR|O_CREAT|O_DIRECT, 0700);
> while( write(tfd, buf, 4096) > 0); /* loop untill ENOSPC */
> fsync(fd); /* just in case */
> while (pos < sz) {
> /* each seek+ write operation result in splits uninitialized extent
> in three extents. Splitting may result in new extent allocation
> which probably will fail because of ENOSPC*/
>
> lseek(fd, blksize*2 -1, SEEK_CUR);
> if ((ret = write(fd, 'a', 1)) != 1)
> exit(1);
> pos += blksize * 2;
> }
>
> Buggy place:
> ~~~~~~~~~~~~
> ext4_ext_get_blocks(..., bh_result,..)
> {
> err = 0;
> allocated = 0;
> ....
> ret = ext4_ext_convert_to_initialized(...)
> if (ret < 0)
> << By occasion real error code was lost here.
> goto out2
> ....
> out2:
> ....
> return err? err: allocated;
> << Wow.. exit with "0", and caller assumes what bh_result was properly filled
> << and then will submit it for write. But in fact bh contains random data in
> << ->b_bdev, ->b_blocknr fileds :).
> }
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> ---
> fs/ext4/extents.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 8528774..fc8e508 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -2320,9 +2320,10 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
> ret = ext4_ext_convert_to_initialized(handle, inode,
> path, iblock,
> max_blocks);
> - if (ret <= 0)
> + if (ret <= 0) {
> + err = ret;
> goto out2;
> - else
> + } else
> allocated = ret;
> goto outnew;
> }
prev parent reply other threads:[~2008-01-10 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 14:31 [PATCH] ext4: fix uniniatilized extend splitting error Dmitry Monakhov
2008-01-10 21:31 ` Andreas Dilger
2008-01-11 1:08 ` Mingming Cao
2008-01-11 9:08 ` Amit K. Arora
2008-01-10 23:42 ` Mingming Cao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1200008575.4012.7.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=adilger@clusterfs.com \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox