Hey Thomas, thank you for looking into this.
On 2 June 2015 at 18:55, Thomas Schwinge tho...@codesourcery.com wrote:
Shame on me, but I've never actively used/built Guix before. I do know
about https://github.com/Phant0mas/Guix-on-Hurd, and that there must be
a Guix manual existing -- but can
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)
On Wed, Jun 03, 2015 at 01:54:40PM +0200, Justus Winter wrote:
I independently rediscovered that host port leak. I see two options
how to proceed:
The host and task ports actually don't leak, because they're unique to
a task, and Mach treats them as exceptions by never overruning the user
Quoting Richard Braun (2015-06-03 14:10:16)
On Wed, Jun 03, 2015 at 01:54:40PM +0200, Justus Winter wrote:
I independently rediscovered that host port leak. I see two options
how to proceed:
The host and task ports actually don't leak, because they're unique to
a task, and Mach treats
