From: Simon Essien <champbreed1@gmail.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, champbreed1@gmail.com
Subject: [PATCH 2/3] man2: update glibc wrapper status and clean up FIXMEs
Date: Tue, 6 Jan 2026 11:47:35 +0000 [thread overview]
Message-ID: <20260106114736.105645-2-champbreed1@gmail.com> (raw)
In-Reply-To: <20260106114736.105645-1-champbreed1@gmail.com>
Update seccomp(2) to reflect that glibc 2.33 added a wrapper.
Update sched_setattr(2) to remove obsolete FIXME markers, as the
lack of a glibc wrapper is already correctly noted in the text.
Signed-off-by: Simon Essien <champbreed1@gmail.com>
---
man/man2/sched_setattr.2 | 5 +----
man/man2/seccomp.2 | 4 ++--
2 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/man/man2/sched_setattr.2 b/man/man2/sched_setattr.2
index 6d5718022..c8010b8fa 100644
--- a/man/man2/sched_setattr.2
+++ b/man/man2/sched_setattr.2
@@ -460,7 +460,6 @@ does not include all CPUs in the system
Linux.
.SH HISTORY
Linux 3.14.
-.\" FIXME . Add glibc version
.SH NOTES
glibc does not provide wrappers for these system calls;
call them using
@@ -482,9 +481,7 @@ provides a superset of the functionality of
and (partially)
.BR getpriority (2).
.SH BUGS
-In Linux versions up to
-.\" FIXME . patch sent to Peter Zijlstra
-3.15,
+In Linux versions up to 3.15,
.BR sched_setattr ()
failed with the error
.B EFAULT
diff --git a/man/man2/seccomp.2 b/man/man2/seccomp.2
index 125794880..685ed4713 100644
--- a/man/man2/seccomp.2
+++ b/man/man2/seccomp.2
@@ -25,7 +25,7 @@ Standard C library
.fi
.P
.IR Note :
-glibc provides no wrapper for
+Before glibc 2.33, glibc provided no wrapper for
.BR seccomp (),
necessitating the use of
.BR syscall (2).
@@ -863,7 +863,7 @@ be determined.
Linux.
.SH HISTORY
Linux 3.17.
-.\" FIXME . Add glibc version
+Glibc 2.33.
.SH NOTES
Rather than hand-coding seccomp filters as shown in the example below,
you may prefer to employ the
--
2.51.0
next prev parent reply other threads:[~2026-01-06 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 11:47 [PATCH 1/3] man3/creal.3, man3/cimag.3: Standardize style and history Simon Essien
2026-01-06 11:47 ` Simon Essien [this message]
2026-01-06 11:47 ` [PATCH 3/3] path_resolution.7: document read-only mounts, ACLs, and immutable files Simon Essien
-- strict thread matches above, loose matches on Subject: below --
2026-01-06 13:49 [PATCH 1/3] man3/creal.3, man3/cimag.3: Standardize style and history Simon Essien
2026-01-06 13:49 ` [PATCH 2/3] man2: update glibc wrapper status and clean up FIXMEs Simon Essien
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=20260106114736.105645-2-champbreed1@gmail.com \
--to=champbreed1@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@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