From: Brian Foster <bfoster@redhat.com>
To: Maxim Patlasov <MPatlasov@parallels.com>
Cc: miklos@szeredi.hu, fuse-devel@lists.sourceforge.net,
avati@redhat.com, linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] fuse: hold i_mutex in fuse_file_fallocate() - v2
Date: Thu, 13 Jun 2013 07:46:00 -0400 [thread overview]
Message-ID: <51B9B0F8.3070301@redhat.com> (raw)
In-Reply-To: <20130613081551.11870.77028.stgit@maximpc.sw.ru>
On 06/13/2013 04:16 AM, Maxim Patlasov wrote:
> Changing size of a file on server and local update (fuse_write_update_size)
> should be always protected by inode->i_mutex. Otherwise a race like this is
> possible:
>
> 1. Process 'A' calls fallocate(2) to extend file (~FALLOC_FL_KEEP_SIZE).
> fuse_file_fallocate() sends FUSE_FALLOCATE request to the server.
> 2. Process 'B' calls ftruncate(2) shrinking the file. fuse_do_setattr()
> sends shrinking FUSE_SETATTR request to the server and updates local i_size
> by i_size_write(inode, outarg.attr.size).
> 3. Process 'A' resumes execution of fuse_file_fallocate() and calls
> fuse_write_update_size(inode, offset + length). But 'offset + length' was
> obsoleted by ftruncate from previous step.
>
> Changed in v2 (thanks Brian and Anand for suggestions):
> - made relation between mutex_lock() and fuse_set_nowrite(inode) more
> explicit and clear.
> - updated patch description to use ftruncate(2) in example
>
> Signed-off-by: Maxim V. Patlasov <MPatlasov@parallels.com>
> ---
Makes more sense and I like the cleanup... thanks.
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/fuse/file.c | 12 ++++++++----
> 1 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> index e570081..35f2810 100644
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -2470,13 +2470,16 @@ static long fuse_file_fallocate(struct file *file, int mode, loff_t offset,
> .mode = mode
> };
> int err;
> + bool lock_inode = !(mode & FALLOC_FL_KEEP_SIZE) ||
> + (mode & FALLOC_FL_PUNCH_HOLE);
>
> if (fc->no_fallocate)
> return -EOPNOTSUPP;
>
> - if (mode & FALLOC_FL_PUNCH_HOLE) {
> + if (lock_inode) {
> mutex_lock(&inode->i_mutex);
> - fuse_set_nowrite(inode);
> + if (mode & FALLOC_FL_PUNCH_HOLE)
> + fuse_set_nowrite(inode);
> }
>
> req = fuse_get_req_nopages(fc);
> @@ -2511,8 +2514,9 @@ static long fuse_file_fallocate(struct file *file, int mode, loff_t offset,
> fuse_invalidate_attr(inode);
>
> out:
> - if (mode & FALLOC_FL_PUNCH_HOLE) {
> - fuse_release_nowrite(inode);
> + if (lock_inode) {
> + if (mode & FALLOC_FL_PUNCH_HOLE)
> + fuse_release_nowrite(inode);
> mutex_unlock(&inode->i_mutex);
> }
>
>
next prev parent reply other threads:[~2013-06-13 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 8:16 [PATCH] fuse: hold i_mutex in fuse_file_fallocate() - v2 Maxim Patlasov
2013-06-13 11:46 ` Brian Foster [this message]
2013-06-17 23:49 ` Miklos Szeredi
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=51B9B0F8.3070301@redhat.com \
--to=bfoster@redhat.com \
--cc=MPatlasov@parallels.com \
--cc=avati@redhat.com \
--cc=devel@openvz.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.