From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org, Jakub Wilk <jwilk@jwilk.net>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH v5] grantpt.3: no-op on modern glibc and other UNIXes
Date: Tue, 18 Jul 2023 01:13:59 +0200 [thread overview]
Message-ID: <7d88523e-d0be-e65e-2dd3-d7776960dde8@kernel.org> (raw)
In-Reply-To: <van5n7dhx63tbicenevvkkg624su7xcsjrffhicjruvmdii4yk@j52kjf6qgwko>
[-- Attachment #1.1: Type: text/plain, Size: 2877 bytes --]
On 2023-07-16 13:55, наб wrote:
> FreeBSD, OpenBSD, and Linux (/dev/ptmx) do all intialisation in open(2),
> and grantpt(3) is a no-op (that checks whether the fd is a pty, except on
> musl).
>
> The illumos gate and NetBSD do a ioctl (and, indeed, illumos-gate commit
> facf4a8d7b59fde89a8662b4f4c73a758e6c402c ("PSARC/2003/246 Filesystem
> Driven Device Naming"), which kills pt_chmod, notes that it's been
> "6464196 bfu should remove pt_chmod, obsoleted by /dev filesystem").
>
> glibc 2.33 completely kills BSD PTY support on Linux
> (Debian hasn't configured with them on any architecture since 2007:
> https://bugs.debian.org/338404
> and even earlier on some arches; they're really just trivia under
> Linux ‒ this may be better served stuffed into HISTORY as an explainer
> for the SIGCHLD thing, since regardless of the "version", the behaviour
> is well-defined and consistent).
>
> Cc: Jakub Wilk <jwilk@jwilk.net>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> I read it but didn't really understand what you were saying, since
> you're on record as a text‒text‒text liker.
> You can trivially continue the lines with \c like the below, but
> "no-op, with permissions ... on Linux, or an ioctl(2)."
> would probably also work just as well,
> and I leave that to your editorial sensibilities.
>
> man3/grantpt.3 | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
>
> diff --git a/man3/grantpt.3 b/man3/grantpt.3
> index a19172a3e..363a7aebd 100644
> --- a/man3/grantpt.3
> +++ b/man3/grantpt.3
> @@ -84,17 +84,15 @@ .SH ATTRIBUTES
> .ad
> .sp 1
> .SH VERSIONS
> -Many systems implement this function via a set-user-ID helper binary
> +Historical systems implemented this function via a set-user-ID helper binary
> called "pt_chown".
> -On Linux systems with a devpts filesystem (present since Linux 2.2),
> -the kernel normally sets the correct ownership and permissions
> -for the pseudoterminal slave when the master is opened
> -.RB ( posix_openpt (3)),
> -so that nothing must be done by
> -.BR grantpt ().
> -Thus, no such helper binary is required
> -(and indeed it is configured to be absent during the
> -glibc build that is typical on many systems).
> +glibc on Linux before glibc 2.33 could do so as well,
> +in order to support configurations with only BSD pseudoterminals;
> +this support has been removed.
> +On modern systems this is either a no-op\c
> +\[em]with permissions configured on pty allotion, as is the case on Linux\[em]\c
> +or an
> +.BR ioctl (2).
I'm thinking that this paragraph deserves to be HISTORYzised, doesn't it?
> .SH STANDARDS
> POSIX.1-2008.
> .SH HISTORY
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-17 23:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 0:14 [PATCH] grantpt.3: no-op on modern glibc and other UNIXes наб
2023-06-19 6:54 ` Jakub Wilk
2023-06-19 22:11 ` [PATCH v2] " наб
2023-07-08 15:54 ` Alejandro Colomar
2023-07-08 19:59 ` [PATCH v3] " наб
2023-07-15 13:32 ` Alejandro Colomar
2023-07-15 18:49 ` [PATCH v4] " наб
2023-07-16 1:09 ` Alejandro Colomar
2023-07-16 11:55 ` [PATCH v5] " наб
2023-07-16 13:46 ` Alejandro Colomar
2023-07-16 14:52 ` наб
2023-07-16 15:11 ` Alejandro Colomar
2023-07-17 23:13 ` Alejandro Colomar [this message]
2023-07-17 23:31 ` [PATCH v6] grantpt.3: no-op on modern glibc and other UNIXes, HISTORYise наб
2023-07-18 11:42 ` Alejandro Colomar
2023-07-18 15:07 ` наб
2023-07-18 21:28 ` 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=7d88523e-d0be-e65e-2dd3-d7776960dde8@kernel.org \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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