Date: Tue, 4 Feb 2003 03:33:32 -0500 (EST) From: "Ilmar S. Habibulin" <ilmar@watson.org> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: What is the difference between p_ucred and td_ucred? Message-ID: <20030204032624.U9181-100000@fledge.watson.org> In-Reply-To: <Pine.NEB.3.96L.1030203120211.80901B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 lock and atomically check the process > credential before updating. If the thread doesn't immediately leave the > kernel (i.e., more checks might be performed), you'll also need to > propagate the cred change to the thread from the process. Ok. Thank you for an expanation, I'll consider that. Now i'm trying to reanimate Thomas Moestls' capability work. Is anybody interested in such integration? I have almost bootable kernel and now will try to understand kernel structures locking and td_ucred/p_ucred interactions, to make nessesary changes. Or SEBSD make capabilities completly unnesessary? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030204032624.U9181-100000>