Re: [PATCH v4 18/19] btrfs: only dirty the inode in btrfs_update_time if something was changed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jeff Layton <jlayton@xxxxxxxxxx>
Subject: Re: [PATCH v4 18/19] btrfs: only dirty the inode in btrfs_update_time if something was changed
From: David Sterba <dsterba@xxxxxxx>
Date: Mon, 8 Jan 2018 18:59:20 +0100
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, bfields@xxxxxxxxxxxx, neilb@xxxxxxx, jack@xxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, tytso@xxxxxxx, adilger.kernel@xxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, darrick.wong@xxxxxxxxxx, david@xxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, clm@xxxxxx, jbacik@xxxxxx, dsterba@xxxxxxxx, linux-integrity@xxxxxxxxxxxxxxx, zohar@xxxxxxxxxxxxxxxxxx, dmitry.kasatkin@xxxxxxxxx, linux-afs@xxxxxxxxxxxxxxxxxxx, dhowells@xxxxxxxxxx, jaltman@xxxxxxxxxxxx
In-reply-to: <20171222120556.7435-19-jlayton@kernel.org>
Mail-followup-to: dsterba@xxxxxxx, Jeff Layton <jlayton@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, bfields@xxxxxxxxxxxx, neilb@xxxxxxx, jack@xxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, tytso@xxxxxxx, adilger.kernel@xxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, darrick.wong@xxxxxxxxxx, david@xxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, clm@xxxxxx, jbacik@xxxxxx, dsterba@xxxxxxxx, linux-integrity@xxxxxxxxxxxxxxx, zohar@xxxxxxxxxxxxxxxxxx, dmitry.kasatkin@xxxxxxxxx, linux-afs@xxxxxxxxxxxxxxxxxxx, dhowells@xxxxxxxxxx, jaltman@xxxxxxxxxxxx
References: <20171222120556.7435-1-jlayton@kernel.org> <20171222120556.7435-19-jlayton@kernel.org>
Reply-to: dsterba@xxxxxxx
User-agent: Mutt/1.5.23.1 (2014-03-12)

On Fri, Dec 22, 2017 at 07:05:55AM -0500, Jeff Layton wrote:
> From: Jeff Layton <jlayton@xxxxxxxxxx>
> 
> At this point, we know that "now" and the file times may differ, and we
> suspect that the i_version has been flagged to be bumped. Attempt to
> bump the i_version, and only mark the inode dirty if that actually
> occurred or if one of the times was updated.
> 
> Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx>

Acked-by: David Sterba <dsterba@xxxxxxxx>

References:
- [PATCH v4 00/19] fs: rework and optimize i_version handling in filesystems
  - From: Jeff Layton
- [PATCH v4 18/19] btrfs: only dirty the inode in btrfs_update_time if something was changed
  - From: Jeff Layton

Prev by Date: Re: [PATCH v4 19/19] fs: handle inode->i_version more efficiently
Next by Date: Re: [PATCH v4 06/19] btrfs: convert to new i_version API
Previous by thread: [PATCH v4 18/19] btrfs: only dirty the inode in btrfs_update_time if something was changed
Next by thread: [PATCH v4 17/19] xfs: avoid setting XFS_ILOG_CORE if i_version doesn't need incrementing
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]