From: Andrey Albershteyn <aalbersh@redhat.com>
To: cem@kernel.org, djwong@kernel.org, linux-xfs@vger.kernel.org
Cc: Andrey Albershteyn <aalbersh@redhat.com>
Subject: [PATCH 0/3] Use new syscalls to set filesystem inode attributes on any inode
Date: Tue, 29 Jul 2025 13:00:34 +0200 [thread overview]
Message-ID: <20250729-xfs-xattrat-v1-0-7b392eee3587@kernel.org> (raw)
With addition of new syscalls file_getattr/file_setattr allow changing
filesystem inode attributes on special files. Fix project ID inheritance
for special files in renames.
Cc: linux-xfs@vger.kernel.org
---
Darrick, I left your reviewed-by tags, as the code didn't changed, I just
updated the commit messages. Let me know if you have any new feedback on
this.
---
Andrey Albershteyn (3):
xfs: allow renames of project-less inodes
xfs: allow setting xattrs on special files
xfs: add .fileattr_set and fileattr_get callbacks for symlinks
fs/xfs/xfs_inode.c | 64 +++++++++++++++++++++++++++++-------------------------
fs/xfs/xfs_ioctl.c | 6 -----
fs/xfs/xfs_iops.c | 2 ++
3 files changed, 36 insertions(+), 36 deletions(-)
---
base-commit: 86aa721820952b793a12fc6e5a01734186c0c238
change-id: 20250320-xfs-xattrat-b31a9f5ed284
Best regards,
--
Andrey Albershteyn <aalbersh@kernel.org>
next reply other threads:[~2025-07-29 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 11:00 Andrey Albershteyn [this message]
2025-07-29 11:00 ` [PATCH 1/3] xfs: allow renames of project-less inodes Andrey Albershteyn
2025-07-29 11:00 ` [PATCH 2/3] xfs: allow setting xattrs on special files Andrey Albershteyn
2025-07-29 14:32 ` Darrick J. Wong
2025-07-29 14:55 ` Andrey Albershteyn
2025-07-29 11:00 ` [PATCH 3/3] xfs: add .fileattr_set and fileattr_get callbacks for symlinks Andrey Albershteyn
2025-07-29 14:34 ` [PATCH 0/3] Use new syscalls to set filesystem inode attributes on any inode Darrick J. Wong
2025-07-29 15:50 ` Andrey Albershteyn
2025-07-29 15:52 ` Darrick J. Wong
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=20250729-xfs-xattrat-v1-0-7b392eee3587@kernel.org \
--to=aalbersh@redhat.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).