From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Weimer Subject: Re: [PATCH v2 0/5] pid: add pidfd_open() Date: Tue, 02 Apr 2019 13:03:24 +0200 Message-ID: <878swsr7nn.fsf@oldenburg2.str.redhat.com> References: <20190330171215.3yrfxwodstmgzmxy@brauner.io> <132107F4-F56B-4D6E-9E00-A6F7C092E6BD@amacapital.net> <20190331211041.vht7dnqg4e4bilr2@brauner.io> <18C7FCB9-2CBA-4237-94BB-9C4395A2106B@amacapital.net> <20190401114059.7gdsvcqyoz2o5bbz@yavin> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Daniel Colascione's message of "Mon, 1 Apr 2019 09:45:22 -0700") Sender: linux-kernel-owner@vger.kernel.org To: Daniel Colascione Cc: Linus Torvalds , Jonathan Kowalski , Aleksa Sarai , Andy Lutomirski , Christian Brauner , Jann Horn , Andrew Lutomirski , David Howells , "Serge E. Hallyn" , Linux API , Linux List Kernel Mailing , Arnd Bergmann , "Eric W. Biederman" , Konstantin Khlebnikov , Kees Cook , Alexey Dobriyan , Thomas Gleixner , Michael Kerrisk-manpages List-Id: linux-api@vger.kernel.org * 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