Re: GSoC: Porting Guix to Hurd week 3+4 report.

Hey Thomas, thank you for looking into this. On 2 June 2015 at 18:55, Thomas Schwinge wrote: > Shame on me, but I've never actively used/built Guix before. I do know > about , and that there must be > a Guix manual existing -- but can you help me get st

Re: mach_task_self, mach_thread_self, mach_host_self

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 tr

Re: mach_task_self, mach_thread_self, mach_host_self

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 spa

Re: mach_task_self, mach_thread_self, mach_host_self

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)