[PATCH] string: New thread-safe strtok version

Cristian Rodríguez cristian@rodriguez.im
Fri Apr 4 12:54:51 GMT 2025


On Fri, Apr 4, 2025 at 9:32 AM Florian Weimer <fweimer@redhat.com> wrote:
> they are still not library-safe, so libraries

Huh..yeah..you are right. I did not consider this bit. some other code
could modify whatever storage behind the user library's back and
pandemonium ensues.

 We could fix that with per-DSO allocates.  Not sure if
> that is necessary.  Maybe adding dup*ent and free*ent plus get* thread
> safety is sufficient.

Is that too difficult? per-dso allocates sound like a nice thing to
have and that will indeed make the issue go away in practice.


More information about the Libc-alpha mailing list