This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Linux: Add gettid system call wrapper [BZ #6399]


On December 10, 2018 1:02:46 PM GMT+01:00, Florian Weimer <fweimer@redhat.com> wrote:
>* Christian Brauner:
>
>> Florian, if this is not just about POSIX but also about the actual
>> implementation could you maybe add a section to the manual what
>> happens when:
>
>> - the thread-group leader exits
>> - the thread-group leader becomes a zombie
>> - whether a thread-group can be reparented
>> ?
>> Obviously all three are closely related.
>
>I lack the technical expertise in this area to do this, but input is
>welcome.  I can probably come up with*

*If* [sic!] pidfd_send_signal() gets in I have
follow up patches that do allow sending signals to process groups and threads.
I've been looking into the exact behavior
of thread-groups and process groups
so I can spend some time documenting it.
I will have to write this down for myself anyway. (If I haven't made it clear: that's a big *if* on whether signaling via fds lands).

> wording.  Some of this should
>perhaps go to the man-pages project because I think the glibc manual
>should document only cases which are possible to observe with the glibc
>implementation (with NPTL using CLONE_THREAD etc.).
>
>I think we really need to document the different effects of returning
>from main (or calling exit directly) on the one hand, and calling
>pthread_exit from the main thread on the other.  Some of the thread
>group behavior could be included in that.

Very much agreed!

Thanks for all the work!
Christian

>
>Thanks,
>Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]