cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: fallocate: do not rely on	file_update_time to mark the inode dirty
Date: Tue, 22 Sep 2015 08:44:53 -0400 (EDT)	[thread overview]
Message-ID: <910644418.31908305.1442925893619.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1442916614-17003-1-git-send-email-anprice@redhat.com>

----- Original Message -----
> Previously __gfs2_fallocate() relied on file_update_time() marking the
> inode dirty, but that's not a safe assumption as that function doesn't
> dirty the inode in some cases. Mark the inode dirty explicitly.
> 
> Signed-off-by: Andrew Price <anprice@redhat.com>
> ---
>  fs/gfs2/file.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
> index cf4ab89..71cd138 100644
> --- a/fs/gfs2/file.c
> +++ b/fs/gfs2/file.c
> @@ -897,8 +897,8 @@ static long __gfs2_fallocate(struct file *file, int mode,
> loff_t offset, loff_t
>  
>  	if (!(mode & FALLOC_FL_KEEP_SIZE) && (pos + count) > inode->i_size) {
>  		i_size_write(inode, pos + count);
> -		/* Marks the inode as dirty */
>  		file_update_time(file);
> +		mark_inode_dirty(inode);
>  	}
>  
>  	return generic_write_sync(file, pos, count);
> --
> 2.4.3

Hi,

Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=4b813f09405823dcbb27a434f6ddcd1741e55e9b

Regards,

Bob Peterson
Red Hat File Systems



      reply	other threads:[~2015-09-22 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 10:10 [Cluster-devel] [PATCH] GFS2: fallocate: do not rely on file_update_time to mark the inode dirty Andrew Price
2015-09-22 12:44 ` Bob Peterson [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=910644418.31908305.1442925893619.JavaMail.zimbra@redhat.com \
    --to=rpeterso@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).