[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <878swsr7nn.fsf@oldenburg2.str.redhat.com>
Date: Tue, 02 Apr 2019 13:03:24 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Daniel Colascione <dancol@...gle.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Jonathan Kowalski <bl0pbl33p@...il.com>,
Aleksa Sarai <cyphar@...har.com>,
Andy Lutomirski <luto@...capital.net>,
Christian Brauner <christian@...uner.io>,
Jann Horn <jannh@...gle.com>,
Andrew Lutomirski <luto@...nel.org>,
David Howells <dhowells@...hat.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Linux API <linux-api@...r.kernel.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
Kees Cook <keescook@...omium.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Michael Kerrisk-manpages <mtk.manpages@...il.com>,
"Dmitry V. Levin" <ldv@...linux.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>,
Nagarathnam Muthusamy <nagarathnam.muthusamy@...cle.com>,
Al Viro <viro@...iv.linux.org.uk>,
Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH v2 0/5] pid: add pidfd_open()
* Daniel Colascione:
> But doesn't the CSIGNAL approach still require that libraries somehow
> coordinate which non-SIGCHLD signal they use? (Signal coordination a
> separate problem, unfortunately.)
There's already an allocation mechanism for realtime signals in glibc,
via __libc_allocate_rtsig. I don't know what it is about: It's clearly
intended as an external interface, yet there isn't a declaration in any
installed header file. ALSA has some optional code to use it, but I
don't think distributions compile ALSA in that way; it always uses SIGIO.
Thanks,
Florian
Powered by blists - more mailing lists