From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Ted Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH RESEND] ext4: make sure O_(D)SYNC semantic in ext4_fallocate()
Date: Thu, 14 Jun 2012 10:43:22 +0800 [thread overview]
Message-ID: <20120614024322.GA5759@gmail.com> (raw)
In-Reply-To: <20120614001531.GB22646@thunk.org>
On Wed, Jun 13, 2012 at 08:15:31PM -0400, Ted Ts'o wrote:
> Hi Zheng,
>
> I finally got around to reviewing this patch and I had one comment
>
> > Ext4 must make sure the transaction to be commited to the disk when
> > user opens a file with O_(D)SYNC flag and do a fallocate(2) call.
> >
> > diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> > index 74f23c2..00e32d9 100644
> > --- a/fs/ext4/extents.c
> > +++ b/fs/ext4/extents.c
> > @@ -4356,6 +4356,8 @@ retry:
> > ret = PTR_ERR(handle);
> > break;
> > }
> > + if (file->f_flags & O_SYNC)
> > + ext4_handle_sync(handle);
> > ret = ext4_map_blocks(handle, inode, &map, flags);
> > if (ret <= 0) {
> > #ifdef EXT4FS_DEBUG
>
> For a large fallocate(), it can require multiple calls to
> ext4_map_blocks(), and we should only sync after we've allocated the
> last segment. We should also not force a sync if there is an error
> allocating blocks. So it seems to me this patch would be better; what
> do you think?
Hi Ted,
Thank you for your review. I agree with you that the following patch is
better.
Regards,
Zheng
> commit b790d70be9515dfaba59b0be0aff373e6867826d
> Author: Zheng Liu <gnehzuil.liu@gmail.com>
> Date: Wed Jun 13 20:15:01 2012 -0400
>
> ext4: honor O_(D)SYNC semantic in ext4_fallocate()
>
> Ext4 must make sure the transaction to be commited to the disk when
> user opens a file with O_(D)SYNC flag and do a fallocate(2) call.
>
> This problem had been reported by Christoph Hellwig in this thread:
> http://www.spinics.net/lists/linux-btrfs/msg13621.html
>
> Reported-by: Christoph Hellwig <hch@infradead.org>
> Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 91341ec..f1089cb 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -4420,6 +4420,8 @@ retry:
> ext4_falloc_update_inode(inode, mode, new_size,
> (map.m_flags & EXT4_MAP_NEW));
> ext4_mark_inode_dirty(handle, inode);
> + if ((file->f_flags & O_SYNC) && ret >= max_blocks)
> + ext4_handle_sync(handle);
> ret2 = ext4_journal_stop(handle);
> if (ret2)
> break;
prev parent reply other threads:[~2012-06-14 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 8:47 [PATCH RESEND] ext4: make sure O_(D)SYNC semantic in ext4_fallocate() Zheng Liu
2012-05-23 1:19 ` Zheng Liu
2012-06-14 0:15 ` Ted Ts'o
2012-06-14 2:43 ` Zheng Liu [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=20120614024322.GA5759@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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).