From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216951] New: close_range(2) page missing; closefrom(2) needs refreshing for glibc inclusion
Date: Thu, 19 Jan 2023 01:45:57 +0000 [thread overview]
Message-ID: <bug-216951-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216951
Bug ID: 216951
Summary: close_range(2) page missing; closefrom(2) needs
refreshing for glibc inclusion
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: sam@gentoo.org
Regression: No
This came up at
https://github.com/OpenRC/openrc/pull/541#discussion_r1070724653.
man-pages currently doesn't document closefrom(2) at all, and is outdated wrt
close_range(2) (it only covers the kernel uapi interface, not the fact it's in
glibc & the relevant headers - in since glibc 2.34.).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-01-19 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 1:45 bugzilla-daemon [this message]
2023-01-19 1:46 ` [Bug 216951] close_range(2) needs refreshing for glibc inclusion; closefrom(2) page missing bugzilla-daemon
2023-05-19 12:49 ` bugzilla-daemon
2023-05-19 12:49 ` bugzilla-daemon
2023-05-24 13:37 ` [Bug 216951] New: close_range(2) page missing; closefrom(2) needs refreshing for glibc inclusion Alyssa Ross
2023-05-24 15:59 ` [Bug 216951] close_range(2) needs refreshing for glibc inclusion; closefrom(2) page missing bugzilla-daemon
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=bug-216951-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 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.