From: Andrey Albershteyn <aalbersh@redhat.com>
To: linux-fsdevel@vgre.kernel.org, linux-xfs@vger.kernel.org
Cc: Andrey Albershteyn <aalbersh@redhat.com>
Subject: [PATCH 0/4] Introduce XFS_IOC_SETFSXATTRAT/XFS_IOC_GETFSXATTRAT ioctls
Date: Thu, 9 May 2024 17:14:56 +0200 [thread overview]
Message-ID: <20240509151459.3622910-2-aalbersh@redhat.com> (raw)
Hi all,
This patchset adds new ioctl for setting/getting inode extended
attributes on special files. This roots from xfs_quota not being
able to set project IDs on special files [1]. New XFS ioctl can be
used directly on filesystem inodes to set project ID.
Corresponding xfsprogs patch will follow.
[1]: https://lore.kernel.org/linux-xfs/20240314170700.352845-3-aalbersh@redhat.com/
Andrey Albershteyn (4):
fs: export copy_fsxattr_from_user()
xfs: allow renames of project-less inodes
xfs: allow setting xattrs on special files
xfs: add XFS_IOC_SETFSXATTRAT and XFS_IOC_GETFSXATTRAT
fs/ioctl.c | 11 ++-
fs/xfs/libxfs/xfs_fs.h | 11 +++
fs/xfs/xfs_inode.c | 15 +++-
fs/xfs/xfs_ioctl.c | 182 ++++++++++++++++++++++++++++++++++++++-
include/linux/fileattr.h | 1 +
5 files changed, 212 insertions(+), 8 deletions(-)
--
2.42.0
next reply other threads:[~2024-05-09 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 15:14 Andrey Albershteyn [this message]
2024-05-09 15:14 ` [PATCH 1/4] fs: export copy_fsxattr_from_user() Andrey Albershteyn
2024-05-09 15:14 ` [PATCH 2/4] xfs: allow renames of project-less inodes Andrey Albershteyn
2024-05-09 23:28 ` Darrick J. Wong
2024-05-10 9:41 ` Andrey Albershteyn
2024-05-09 15:14 ` [PATCH 3/4] xfs: allow setting xattrs on special files Andrey Albershteyn
2024-05-09 23:34 ` Darrick J. Wong
2024-05-10 9:46 ` Andrey Albershteyn
2024-05-09 15:15 ` [PATCH 4/4] xfs: add XFS_IOC_SETFSXATTRAT and XFS_IOC_GETFSXATTRAT Andrey Albershteyn
2024-05-09 23:25 ` Darrick J. Wong
2024-05-10 10:38 ` Andrey Albershteyn
2024-05-09 23:55 ` Dave Chinner
2024-05-10 9:37 ` Andrey Albershteyn
2024-05-10 4:58 ` Christoph Hellwig
2024-05-10 9:50 ` Andrey Albershteyn
2024-05-10 15:10 ` 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=20240509151459.3622910-2-aalbersh@redhat.com \
--to=aalbersh@redhat.com \
--cc=linux-fsdevel@vgre.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).