From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc at the Toolchains microconference at LPC 2019
Date: Wed, 26 Jun 2019 13:40:53 -0400 [thread overview]
Message-ID: <CAKCAbMj4DoZzeaTux9kN3mybmpW8Q=Kv0=vynpT8gcJBbtmMEQ@mail.gmail.com> (raw)
In-Reply-To: <87imss1e13.fsf@oldenburg2.str.redhat.com>
On Wed, Jun 26, 2019 at 12:56 PM Florian Weimer <fweimer@redhat.com> wrote:
> * Zack Weinberg:
> > Well, _I_ think glibc should provide wrappers for all Linux system
> > calls, except those that cannot be used without stomping on internal
> > glibc data structures (e.g. set_tid_address, set_robust_list, brk) and
> > those that have been completely superseded by newer syscalls. Other
> > people have disagreed with me pretty strenuously, but they haven't
> > done any of the work required to make forward progress on their more
> > conservative policies. I am tempted to post a patch early in the 2.31
> > cycle that adds wrappers for everything, and then threaten to apply it
> > unilaterally unless I hear concrete objections within a week or so.
>
> In my experience, it's been difficult to get reviewers. So what the
> project says it wants and what the project actually makes happen is
> rather different.
For the record, the shade in my message was not aimed at you. I think
you're one of the only people who's managed to make forward progress
on adding syscall wrappers in the past several years.
zw
next prev parent reply other threads:[~2019-06-26 17:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 16:01 glibc at the Toolchains microconference at LPC 2019 Florian Weimer
2019-06-26 16:39 ` Dmitry V. Levin
2019-06-26 16:50 ` Zack Weinberg
2019-06-26 16:56 ` Florian Weimer
2019-06-26 17:40 ` Zack Weinberg [this message]
2019-06-26 20:33 ` Carlos O'Donell
2019-06-26 20:39 ` Christian Brauner
2019-06-26 20:58 ` Carlos O'Donell
2019-06-26 17:28 ` Yann Droneaud
2019-06-26 17:41 ` Christian Brauner
2019-06-26 21:04 ` Carlos O'Donell
2019-06-27 9:39 ` Dmitry V. Levin
2019-06-27 10:05 ` Szabolcs Nagy
2019-06-27 10:18 ` Christian Brauner
2019-06-27 13:05 ` Dmitry V. Levin
2019-06-27 15:57 ` Zack Weinberg
2019-06-27 17:21 ` Florian Weimer
2019-06-27 20:07 ` Carlos O'Donell
2019-06-27 20:53 ` wrappers for multiplexed syscalls (was Re: glibc at the Toolchains microconference at LPC 2019) Dmitry V. Levin
2019-06-27 21:22 ` Florian Weimer
2019-06-28 21:20 ` Dmitry V. Levin
2019-06-28 21:35 ` Florian Weimer
2019-06-29 1:52 ` Zack Weinberg
2019-06-29 6:27 ` Florian Weimer
2019-06-27 13:22 ` glibc at the Toolchains microconference at LPC 2019 Zack Weinberg
2019-06-27 14:10 ` syscall wrappers policy (was re: glibc at the Toolchains microconference) Zack Weinberg
2019-06-27 15:48 ` DJ Delorie
2019-06-27 16:02 ` Zack Weinberg
2019-06-27 16:50 ` Carlos O'Donell
2019-06-27 17:45 ` glibc at the Toolchains microconference at LPC 2019 Maciej Rozycki
2019-07-08 12:57 ` Florian Weimer
2019-07-08 16:06 ` Paul Eggert
2019-07-19 11:49 ` Florian Weimer
2019-09-14 4:33 ` Maciej W. Rozycki
2019-09-14 11:53 ` Dmitry V. Levin
2019-09-14 14:02 ` Maciej W. Rozycki
2019-07-09 0:14 ` Dmitry V. Levin
2019-09-16 13:26 ` Christian Brauner
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='CAKCAbMj4DoZzeaTux9kN3mybmpW8Q=Kv0=vynpT8gcJBbtmMEQ@mail.gmail.com' \
--to=zackw@panix.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).