From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/3] Linux: Rework Linux PTY support
Date: Wed, 27 May 2020 12:14:10 +0200 [thread overview]
Message-ID: <cover.1590574208.git.fweimer@redhat.com> (raw)
BSD terminal support is pretty much always compiled out in the kernel,
and /dev does not contain the matching device nodes. Therefore, the
fallback code is unused.
Tested on x86_64-linux-gnu.
Florian Weimer (3):
login/tst-grantpt: Convert to support framework, more error checking
Linux: unlockpt needs to fail with EINVAL, not ENOTTY (bug 26053)
Linux: Require properly configured /dev/pts for PTYs
NEWS | 12 ++++
login/tst-grantpt.c | 105 +++++++++++++++++++----------
sysdeps/unix/sysv/linux/getpt.c | 67 +-----------------
sysdeps/unix/sysv/linux/grantpt.c | 73 ++++++++++----------
sysdeps/unix/sysv/linux/ptsname.c | 95 ++------------------------
sysdeps/unix/sysv/linux/unlockpt.c | 21 ++----
6 files changed, 130 insertions(+), 243 deletions(-)
--
2.25.4
next reply other threads:[~2020-05-27 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 10:14 Florian Weimer via Libc-alpha [this message]
2020-05-27 10:14 ` [PATCH 1/3] login/tst-grantpt: Convert to support framework, more error checking Florian Weimer via Libc-alpha
2020-10-02 17:08 ` Adhemerval Zanella via Libc-alpha
2020-05-27 10:14 ` [PATCH 2/3] Linux: unlockpt needs to fail with EINVAL, not ENOTTY (bug 26053) Florian Weimer via Libc-alpha
2020-10-02 17:10 ` Adhemerval Zanella via Libc-alpha
2020-05-27 10:14 ` [PATCH 3/3] Linux: Require properly configured /dev/pts for PTYs Florian Weimer via Libc-alpha
2020-05-27 10:31 ` Christian Brauner
2020-10-02 17:20 ` Adhemerval Zanella via Libc-alpha
2020-10-02 17:26 ` Florian Weimer via Libc-alpha
2020-10-07 9:31 ` Florian Weimer via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1590574208.git.fweimer@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).