Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Andrey Albershteyn <aalbersh@kernel.org>
To: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>, djwong@kernel.org
Subject: [PATCH] man: document that XFS_IOC_FS[G|S]ETXATTR can not be used on special files
Date: Fri, 11 Sep 2026 13:47:44 +0200	[thread overview]
Message-ID: <20260911114746.343945-1-aalbersh@kernel.org> (raw)

Add a CAVEATS section with an note that these ioctls can not be used on
special files and leave a reference to an alternative pathname based
syscall interface.

Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
---
 man/man2/ioctl_xfs_fsgetxattr.2 | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/man/man2/ioctl_xfs_fsgetxattr.2 b/man/man2/ioctl_xfs_fsgetxattr.2
index 25a9ba7965d1..5d223138e419 100644
--- a/man/man2/ioctl_xfs_fsgetxattr.2
+++ b/man/man2/ioctl_xfs_fsgetxattr.2
@@ -238,6 +238,23 @@ Caller did not have permission to change the attributes.
 This API is implemented by the ext4, xfs, btrfs, and f2fs filesystems on the
 Linux kernel.
 Not all fields may be understood by filesystems other than xfs.
+.SH CAVEATS
+The
+.B XFS_IOC_FSGETXATTR
+and
+.B XFS_IOC_FSSETXATTR
+.BR ioctl (2)
+operations require the user to open the file, but this may not be possible or
+lead to side effects on special files such as FIFOs, sockets, block devices,
+character devices, and symlinks.
+.P
+For a pathname based interface see
+.BR file_getattr (2)
+and
+.BR file_setattr (2)
+syscalls.
 .SH SEE ALSO
 .BR ioctl (2),
-.BR ioctl_iflags (2)
+.BR ioctl_iflags (2),
+.BR file_getattr (2),
+.BR file_setattr (2)
-- 
2.55.0


             reply	other threads:[~2026-09-11 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 11:47 Andrey Albershteyn [this message]
2026-09-11 12:29 ` [PATCH] man: document that XFS_IOC_FS[G|S]ETXATTR can not be used on special files 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=20260911114746.343945-1-aalbersh@kernel.org \
    --to=aalbersh@kernel.org \
    --cc=alx@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