[PATCH] pthread_detach: add a comment about a known segfault bug.

[Adhemerval Zanella Netto]

On 23/11/25 19:44, Aaron Jacobs wrote:
> On Mon, Nov 24, 2025 at 8:40 AM Sam James <sam@gentoo.org> wrote:
>> You should include a reference to the bug in the commit
> 
> I don't actually know the process here; how do I provide an updated patch?
> 
> 
>> but that aside,
>> azanella posted https://sourceware.org/bugzilla/show_bug.cgi?id=19951#c5
>> and asked for someone who is interested to take a look. Why don't you?
> 
> I'd be happy to help if I could, but I have no expertise on the
> internals of the library or any ownership or ability to commit. I'm
> just here because I tripped over the bug and want to document it. I
> understand the bug at a high level, but I've never looked at the
> source code before.
> 
> Obviously it's better if the bug actually gets fixed, but I don't
> think that should block documenting the bug -- it's already been
> months since that comment.

Hi,

The last patchset iteration can be found at [1], but unfortunately it does
not apply clean because of recent internal atomic cleanup.  I have created
a personal branch [2], which should be easier to test.

And I do not think adding a comment to bug report improves much here. We
already have a bug report with a lot of background, and a proposed solution.

[1] https://patchwork.sourceware.org/project/glibc/list/?series=50344
[2] https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/azanella/bz28267-bz19951-pthread_detach