[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: port reference leaks (was: Re: new interfaces io_close, io_reidentif
From: |
Thomas Bushnell, BSG |
Subject: |
Re: port reference leaks (was: Re: new interfaces io_close, io_reidentify, file_record_lock |
Date: |
05 Dec 2002 23:07:32 -0800 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Marcus Brinkmann <address@hidden> writes:
> The trick is that ports in Hurd-L4 are managed by the Hurd servers
> themselves, not by the kernel. This means you have more knowledge about who
> provides which object, and who sends you messages, and you can be more
> paranoid to avoid circular references.
Yeah, from the bit that I know of L4, it does sound like this would
work much better there. (Provided, of course, that all the right
security guarantees can still be honored, especially the one that
users don't need to trust servers.)
- port reference leaks (was: Re: new interfaces io_close, io_reidentify, file_record_lock, Marcus Brinkmann, 2002/12/03
- Re: port reference leaks (was: Re: new interfaces io_close, io_reidentify, file_record_lock, Thomas Bushnell, BSG, 2002/12/03
- Re: port reference leaks (was: Re: new interfaces io_close, io_reidentify, file_record_lock, Marcus Brinkmann, 2002/12/04
- Re: port reference leaks (was: Re: new interfaces io_close, io_reidentify, file_record_lock, Marcus Brinkmann, 2002/12/04
- Re: port reference leaks (was: Re: new interfaces io_close, io_reidentify, file_record_lock,
Thomas Bushnell, BSG <=