linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: tytso@mit.edu, adilger.kernel@dilger.ca, djwong@kernel.org,
	david@fromorbit.com, trondmy@hammerspace.com, neilb@suse.de,
	viro@zeniv.linux.org.uk, zohar@linux.ibm.com, xiubli@redhat.com,
	chuck.lever@oracle.com, lczerner@redhat.com, jack@suse.cz,
	bfields@fieldses.org, brauner@kernel.org, fweimer@redhat.com
Cc: linux-api@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	ceph-devel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: [PATCH v4 0/6] vfs: clean up i_version behavior and expose it via statx
Date: Wed,  7 Sep 2022 07:33:12 -0400	[thread overview]
Message-ID: <20220907113318.21810-1-jlayton@kernel.org> (raw)

v4: drop xfs patch
    revise comment update patch with latest proposed semantics

This is a small revision to the patchset I sent a little over a week
ago [1]. Since then, this has also garnered a LWN article [2], so I
won't go into great detail on the basic premise and rationale.

The biggest change here is that I've dropped the xfs patch. Dave Chinner
stated that they'd need to add a new on-disk field instead of modifying
the behavior of the existing di_changecount field [3]. I'll leave that
to the xfs devs, but this does mean that xfs will have "buggy" behavior
until that's done.

I've also sent a revised manpage patchset separately to make sure that
the semantics are acceptable [4]. That hasn't gotten a lot of comments,
so I'm operating under the assumption that the semantics proposed there
are acceptable to most.

[1]: https://lore.kernel.org/linux-nfs/20220826214703.134870-1-jlayton@kernel.org/
[2]: https://lwn.net/Articles/905931/
[3]: https://lore.kernel.org/linux-nfs/20220830000851.GV3600936@dread.disaster.area/
[4]: https://lore.kernel.org/linux-nfs/20220907111606.18831-1-jlayton@kernel.org/T/#u

Jeff Layton (6):
  iversion: update comments with info about atime updates
  ext4: fix i_version handling in ext4
  ext4: unconditionally enable the i_version counter
  vfs: report an inode version in statx for IS_I_VERSION inodes
  nfs: report the inode version in statx if requested
  ceph: fill in the change attribute in statx requests

 fs/ceph/inode.c           | 14 +++++++++-----
 fs/ext4/inode.c           | 15 +++++----------
 fs/ext4/ioctl.c           |  4 ++++
 fs/ext4/move_extent.c     |  6 ++++++
 fs/ext4/super.c           | 13 ++++---------
 fs/ext4/xattr.c           |  1 +
 fs/nfs/inode.c            |  7 +++++--
 fs/stat.c                 |  7 +++++++
 include/linux/iversion.h  | 10 ++++++++--
 include/linux/stat.h      |  1 +
 include/uapi/linux/stat.h |  3 ++-
 samples/vfs/test-statx.c  |  8 ++++++--
 12 files changed, 58 insertions(+), 31 deletions(-)

-- 
2.37.3


             reply	other threads:[~2022-09-07 11:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 11:33 Jeff Layton [this message]
2022-09-07 11:33 ` [PATCH v4 1/6] iversion: update comments with info about atime updates Jeff Layton
2022-09-07 11:33 ` [PATCH v4 2/6] ext4: fix i_version handling in ext4 Jeff Layton
2022-09-07 11:33 ` [PATCH v4 3/6] ext4: unconditionally enable the i_version counter Jeff Layton
2022-09-07 11:33 ` [PATCH v4 4/6] vfs: report an inode version in statx for IS_I_VERSION inodes Jeff Layton
2022-09-07 11:33 ` [PATCH v4 5/6] nfs: report the inode version in statx if requested Jeff Layton
2022-09-07 11:33 ` [PATCH v4 6/6] ceph: fill in the change attribute in statx requests Jeff Layton

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=20220907113318.21810-1-jlayton@kernel.org \
    --to=jlayton@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=bfields@fieldses.org \
    --cc=brauner@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fweimer@redhat.com \
    --cc=jack@suse.cz \
    --cc=lczerner@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=trondmy@hammerspace.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xiubli@redhat.com \
    --cc=zohar@linux.ibm.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).