From: Alejandro Colomar <alx@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Andrey Albershteyn <aalbersh@kernel.org>,
linux-man@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls
Date: Thu, 10 Sep 2026 18:50:46 +0200 [thread overview]
Message-ID: <aqLfs-6crlKiqZw9@devuan> (raw)
In-Reply-To: <20260910164428.GF6238@frogsfrogsfrogs>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
Hi Darrick,
> Date: 2026-09-10 09:44:28-0700
> From: "Darrick J. Wong" <djwong@kernel.org>
>
[...]
> > > > Should we document FS_IOC_FSGETXATTR in a new FS_IOC_FSGETXATTR(2const)
> > > > manual page?
> > >
> > > https://www.man7.org/linux/man-pages/man2/ioctl_xfs_fssetxattr.2.html
> >
> > Thanks! I didn't know that page.
> >
> > I see the page uses the constants as XFS_ instead of FS_? I think the
>
> The sorded history of the xfs(ish) file attributes calls is that they
> began their lives as XFS_IOC_FSGETXATTR since they were XFS-specific.
> Then we tried to make them "generic" by removing the 'X', and that's how
> we got FS_IOC_FSGETXATTR. Finally Andrey came along and made them
> proper syscalls with path-lookup abilities ... but for now they use the
> same struct as the old XFS_IOC_FSGETXATTR.
>
> Personally I think we should only document XFS_IOC_FSGETXATTR (in
> xfsprogs) and file_getattr (in man-pages). And leave FS_IOC_FSGETXATTR
> unmentioned.
>
[...]
>
> quotactl (and xattrs) have a similar weird history of originating in XFS
> and later getting yanked into the vfs. Every time I have to go look up
> the quota syscalls I just get a headache. :/
Thanks! That makes sense. :)
Cheers,
Alex
>
> --D
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-10 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 10:41 [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls Andrey Albershteyn
2026-09-10 13:20 ` Alejandro Colomar
2026-09-10 16:12 ` Darrick J. Wong
2026-09-10 16:31 ` Alejandro Colomar
2026-09-10 16:44 ` Darrick J. Wong
2026-09-10 16:50 ` Alejandro Colomar [this message]
2026-09-10 22:38 ` quotactl(2) (was: [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls) Alejandro Colomar
2026-09-15 18:10 ` Darrick J. Wong
2026-09-15 20:46 ` Alejandro Colomar
2026-09-11 11:17 ` [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls Andrey Albershteyn
2026-09-11 11:56 ` Alejandro Colomar
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=aqLfs-6crlKiqZw9@devuan \
--to=alx@kernel.org \
--cc=aalbersh@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.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 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.