On Mon, 3 Feb 2003, Robert Watson wrote:
The strategy for selecting a credential to check against is generally to
use td_ucred, and to hold no locks. You'll see that suser() does this,
for example. Under some circumstances: specifically, credential updates,
you need to hold the process
On Tue, 4 Feb 2003, Ilmar S. Habibulin wrote:
On Mon, 3 Feb 2003, Robert Watson wrote:
The strategy for selecting a credential to check against is generally to
use td_ucred, and to hold no locks. You'll see that suser() does this,
for example. Under some circumstances: specifically,
Why not to use only credits for proc and make td_ucred macro like
td_proc-p_ucred? Or it has some meaning that i do not understand?
Thank you for help.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Apparently, On Mon, Feb 03, 2003 at 09:08:41AM -0500,
Ilmar S. Habibulin said words to the effect of;
Why not to use only credits for proc and make td_ucred macro like
td_proc-p_ucred? Or it has some meaning that i do not understand?
td_ucred is a read only reference to p_ucred, so
On Mon, 3 Feb 2003, Ilmar S. Habibulin wrote:
Why not to use only credits for proc and make td_ucred macro like
td_proc-p_ucred? Or it has some meaning that i do not understand?
td_ucred is a cached copy of p_ucred. The cached copy is potentially
updated on any entry to the kernel. The
