Re: [RFC PATCH glibc 27/34] hurd: Don't leak __hurd_reply_port0

2023-04-10 Thread Samuel Thibault
Applied, thanks! Sergey Bugaev, le dim. 19 mars 2023 18:10:10 +0300, a ecrit: > Previously, once we set up TLS, we would implicitly switch from using > __hurd_reply_port0 to reply_port inside the TCB, leaving the former > unused. But we never deallocated it, so it got leaked. > > Instead, migrate

[RFC PATCH glibc 27/34] hurd: Don't leak __hurd_reply_port0

2023-03-19 Thread Sergey Bugaev
Previously, once we set up TLS, we would implicitly switch from using __hurd_reply_port0 to reply_port inside the TCB, leaving the former unused. But we never deallocated it, so it got leaked. Instead, migrate the port into the new TCB's reply_port slot. This avoids both the port leak and an extra