Hello, I independently rediscovered that host port leak. I see two options how to proceed:
1/ Cache the port in the libc like we do for the task port. 2/ Cache/deallocate the port everywhere. Given the fact that I found not a single call site of `mach_host_self' (in both the Hurd and the libc) that deallocated the port, the expectation clearly seems to be that `mach_host_self' works like `mach_task_self'. Shall we be pragmatic about it and go with 1/? Justus
