From: Jeff Layton <jlayton@kernel.org>
To: viro@zeniv.linux.org.uk
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
ceph-devel@vger.kernel.org
Subject: [PATCH 3/4] afs: fill out change attribute in statx replies
Date: Tue, 16 Aug 2022 09:27:58 -0400 [thread overview]
Message-ID: <20220816132759.43248-4-jlayton@kernel.org> (raw)
In-Reply-To: <20220816132759.43248-1-jlayton@kernel.org>
Always copy the change attribute in a statx reply, and set the
STATX_CHGATTR bit unconditionally.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
fs/afs/inode.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/afs/inode.c b/fs/afs/inode.c
index 6d3a3dbe4928..bc65cc2dd2d5 100644
--- a/fs/afs/inode.c
+++ b/fs/afs/inode.c
@@ -762,6 +762,8 @@ int afs_getattr(struct user_namespace *mnt_userns, const struct path *path,
do {
read_seqbegin_or_lock(&vnode->cb_lock, &seq);
generic_fillattr(&init_user_ns, inode, stat);
+ stat->change_attr = inode_peek_iversion_raw(inode);
+ stat->result_mask |= STATX_CHANGE_ATTR;
if (test_bit(AFS_VNODE_SILLY_DELETED, &vnode->flags) &&
stat->nlink > 0)
stat->nlink -= 1;
--
2.37.2
next prev parent reply other threads:[~2022-08-16 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 13:27 [PATCH 0/4] vfs: expose the inode change attribute via statx Jeff Layton
2022-08-16 13:27 ` [PATCH 1/4] vfs: report change attribute in statx for IS_I_VERSION inodes Jeff Layton
2022-08-16 13:44 ` Christian Brauner
2022-08-16 13:52 ` Jeff Layton
2022-08-16 13:55 ` David Howells
2022-08-16 14:02 ` Jeff Layton
2022-08-16 15:15 ` David Howells
2022-08-16 15:32 ` Jeff Layton
2022-08-16 15:51 ` Darrick J. Wong
2022-08-16 16:05 ` Jeff Layton
2022-08-18 20:24 ` Jeff Layton
2022-08-16 13:27 ` [PATCH 2/4] nfs: report the change attribute if requested Jeff Layton
2022-08-16 13:27 ` Jeff Layton [this message]
2022-08-16 13:27 ` [PATCH 4/4] 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=20220816132759.43248-4-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.