From: Daniel Tang <danielzgtg.opensource@gmail.com>
To: linux-man@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Aleksa Sarai <cyphar@cyphar.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH] mount_setattr.2: Fix nonexistent perf_setattr
Date: Sun, 15 Nov 2026 22:33:16 -0500 [thread overview]
Message-ID: <6099049.DvuYhMxLoT@daniel-desktop3> (raw)
The problematic reference had been copied from openat2.2, where it was
fixed in bbed82c0693a ("openat2.2: tfix: fix minor reference typo"). I
performed the same fix for mount_setattr.2.
Fixes: f3a5ba3f0151 ("mount_setattr.2: New manual page documenting the mount_setattr() system call")
Link: https://lore.kernel.org/linux-man/20200929223509.11783-2-cyphar@cyphar.com/
Link: https://lore.kernel.org/linux-man/20191003145542.17490-1-cyphar@cyphar.com/
Link: https://lore.kernel.org/linux-man/20210730094121.3252024-1-brauner@kernel.org/
Signed-off-by: Daniel Tang <danielzgtg.opensource@gmail.com>
---
man2/mount_setattr.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
index 77233f589..5f26119cc 100644
--- a/man2/mount_setattr.2
+++ b/man2/mount_setattr.2
@@ -786,7 +786,7 @@ acting as an implicit version number.
(Because new extension fields will always
be appended, the structure size will always increase.)
This extensibility design is very similar to other system calls such as
-.BR perf_setattr (2),
+.BR sched_setattr (2),
.BR perf_event_open (2),
.BR clone3 (2)
and
--
2.53.0
next reply other threads:[~2026-11-16 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 3:33 Daniel Tang [this message]
2026-11-17 0:03 ` [PATCH] mount_setattr.2: Fix nonexistent perf_setattr Alejandro Colomar
2026-11-17 0:17 ` [PATCH v2] " Daniel Tang
2026-11-17 0:23 ` 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=6099049.DvuYhMxLoT@daniel-desktop3 \
--to=danielzgtg.opensource@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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.