[lkml]   [2002]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: problems with changing UID/GID
>>>>> " " == Chris Wedgwood <> writes:

> On Mon, Aug 26, 2002 at 06:16:59PM +0100, Alan Cox wrote:
> It changes the whole semantics of every security test in
> Linux, and breaks most of them totally. Our syscalls know
> the uid is constant during the call

> Could we not (eventually) have CLONE_CREDs and then lock using
> task->cred->lock or whatever? Or might there be cases where
> this will deadlock? It does mean set[eu]id will have to wait
> of other threads and IO to complete... no matter how long that
> takes, but other than might it be reasonable?

Locking does absolutely nothing for the problem of checking file
access with one set of credentials, and then doing the subsequent file
operation with another set of credentials.

->permission(), ->lookup(), ->create(), ->read(), etc.. may all sleep,
giving some alternate thread ample time to change uid/gid/... behind
your back.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.109 / U:19.448 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site