From: Mingming Cao <cmm@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Eric Sandeen <sandeen@redhat.com>, ext4 <linux-ext4@vger.kernel.org>
Subject: Re: BUG with delayed allocation
Date: Thu, 20 Mar 2008 10:29:50 -0700 [thread overview]
Message-ID: <1206034190.3637.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20080320053902.GD6967@skywalker>
On Thu, 2008-03-20 at 11:09 +0530, Aneesh Kumar K.V wrote:
> > Could you try the following patch? It updates the i_disksize at the
> > write_end time.
> >
>
> I will test the patch and update you. BTW shouldn't we update
> i_disksize only after actual block got allocated ?
>
>
Hmm...I am not 100% sure but I think we should not to change the
behavior that the on-disk inode size should be updated when write()
returns to user. Right now the in-memory inode size is updated, user
would expecting the same when they run e2fsck, but e2fsck reads inode
size from disk. Pushing the inode i_disksize update at the writeout
(allocation) time will cause the window that i_size is different than
the i_disksize being enlarged quite big.
Mingming
> >
> > Signed-off-by: Mingming Cao <cmm@us.ibm.com>
> > ---
> > fs/ext4/inode.c | 39 ++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 38 insertions(+), 1 deletion(-)
> >
> > Index: linux-2.6.25-rc5/fs/ext4/inode.c
> > ===================================================================
> > --- linux-2.6.25-rc5.orig/fs/ext4/inode.c 2008-03-19 17:32:44.000000000 -0700
> > +++ linux-2.6.25-rc5/fs/ext4/inode.c 2008-03-19 17:43:19.000000000 -0700
> > @@ -1355,6 +1355,43 @@ static int ext4_writeback_write_end(stru
> > return ret ? ret : copied;
> > }
> >
> > +static int ext4_da_write_end(struct file *file,
> > + struct address_space *mapping,
> > + loff_t pos, unsigned len, unsigned copied,
> > + struct page *page, void *fsdata)
> > +{
> > + handle_t *handle;
> > + struct inode *inode = file->f_mapping->host;
> > + int needed_blocks = ext4_writepage_trans_blocks(inode);
> > + int ret = 0, ret2;
> > + loff_t new_i_size;
> > +
> > + handle = ext4_journal_start(inode, needed_blocks);
> > + if (IS_ERR(handle)) {
> > + unlock_page(page);
> > + page_cache_release(page);
> > + ret = PTR_ERR(handle);
> > + return ret;
> > + }
> > +
> > + new_i_size = pos + copied;
> > + if (new_i_size > EXT4_I(inode)->i_disksize)
> > + EXT4_I(inode)->i_disksize = new_i_size;
> > +
> > + copied = ext4_generic_write_end(file, mapping, pos, len, copied,
> > + page, fsdata);
> > + if (copied < 0)
> > + ret = copied;
> > +
> > + ret2 = ext4_journal_stop(handle);
> > + if (!ret)
> > + ret = ret2;
> > + unlock_page(page);
> > + page_cache_release(page);
> > +
> > + return ret ? ret : copied;
> > +}
> > +
> > static int ext4_journalled_write_end(struct file *file,
> > struct address_space *mapping,
> > loff_t pos, unsigned len, unsigned copied,
> > @@ -2020,7 +2057,7 @@ static const struct address_space_operat
> > .writepages = ext4_da_writepages,
> > .sync_page = block_sync_page,
> > .write_begin = ext4_da_write_begin,
> > - .write_end = generic_write_end,
> > + .write_end = ext4_da_write_end,
> > .bmap = ext4_bmap,
> > .invalidatepage = ext4_da_invalidatepage,
> > .releasepage = ext4_releasepage,
> >
> >
>
> -aneesh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-20 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 8:52 BUG with delayed allocation Aneesh Kumar K.V
2008-03-19 14:42 ` Eric Sandeen
2008-03-19 18:32 ` Aneesh Kumar K.V
2008-03-20 4:21 ` Aneesh Kumar K.V
2008-03-20 0:46 ` Mingming Cao
2008-03-20 5:39 ` Aneesh Kumar K.V
2008-03-20 17:29 ` Mingming Cao [this message]
2008-03-20 17:56 ` Aneesh Kumar K.V
2008-03-20 23:55 ` Andreas Dilger
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=1206034190.3637.25.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).