From: Andrey Albershteyn <aalbersh@kernel.org>
To: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>,
linux-api@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: [PATCH v6 0/2] Introduce man pages for file_getattr() and file_setattr()
Date: Wed, 21 Oct 2026 16:10:03 +0200 [thread overview]
Message-ID: <20261021141010.314835-1-aalbersh@kernel.org> (raw)
Hi folks,
This series introduce 2 man pages for file_getattr() and file_setattr()
syscalls.
Changes from v5:
- rebase to 6.20 and dropped "struct file_attr" patch (merged)
- change description of dirfd & path args to reference openat(2)
Changes from v4:
- Split single patch into 3 separate ones
- Mark examples for linters
- Use special char for empty lines in examples
- Use w64/w32 in printf() in examples
- Use const fattr in file_setattr() definition
- Other minor fixes
- A few fixes found by lint in examples
Changes from v3:
- dropped VERSIONS section in file_attr.2type
- reference arguments and errors from file_setattr to file_getattr
- Minor wording fixes
- Minor formatting fixes
- Removed zero-initialized requirement
- Interdiff with v3 below
Changes from v2:
- a few grammar fixes
- styling fixes
- sashiko.dev fixes (wrong AT_FDCWD combined with AT_EMPTY_PATH
description, unused "dfd")
- dropped requirement to zero fattr before using file_setattr()
- Pathname -> path
- Dropped description of why FS_IOC_ aren't usable with special files
- Fixed backslashes in the code examples
Andrey Albershteyn (2):
man/man2: introduce man page for file_getattr(2) syscall
man/man2: introduce man page for file_setattr(2) syscall
man/man2/file_getattr.2 | 252 ++++++++++++++++++++++++++++++++++++++++
man/man2/file_setattr.2 | 183 +++++++++++++++++++++++++++++
2 files changed, 435 insertions(+)
create mode 100644 man/man2/file_getattr.2
create mode 100644 man/man2/file_setattr.2
Range-diff against v5:
1: bfff306908cf ! 1: c7df8a930c70 man/man2: introduce man page for file_getattr(2) syscall
@@ man/man2/file_getattr.2 (new)
+of the file
+specified by path.
+.P
-+As with
++The
++.I dirfd
++and
++.I path
++arguments behave in the same way as in
+.BR openat (2),
-+if
++with the difference that
+.I path
-+is relative,
-+then it is interpreted relative to the directory
-+referred to by the file descriptor
-+.IR dirfd .
-+The special
-+.I dirfd
-+value
-+.B AT_FDCWD
-+can be used to refer to the current working directory of the calling process.
-+If
-+.I path
-+is absolute,
-+then
-+.I dirfd
-+is ignored.
++can be NULL meaning an empty string.
+.P
+The
+.I fattr
2: d81d763c4223 = 2: 9c7fbaab27e5 man/man2: introduce man page for file_setattr(2) syscall
--
2.56.0
next reply other threads:[~2026-10-21 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 14:10 Andrey Albershteyn [this message]
2026-10-21 14:10 ` [PATCH v6 1/2] man/man2: introduce man page for file_getattr(2) syscall Andrey Albershteyn
2026-10-23 11:28 ` Alejandro Colomar
2026-10-21 14:10 ` [PATCH v6 2/2] man/man2: introduce man page for file_setattr(2) syscall Andrey Albershteyn
2026-10-23 13: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=20261021141010.314835-1-aalbersh@kernel.org \
--to=aalbersh@kernel.org \
--cc=alx@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.