[lkml]   [2002]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2.5.30+] Second attempt at a shared credentials patch
>>>>> " " == Dave McCracken <> writes:

>> Instead of doing this as one big unreadable monolithic patch
>> and risking getting things wrong like in the above case, it
>> would be nice if you could go via a set of wrapper functions:
>> # define get_current_uid() (current->uid) define
>> # set_current_uid(a) current->uid = a

> I don't see this as a win. I *could* do a big monolithic patch
> to change all references to current->*id to macros, then change
> the macros in a separate patch. But then we'd be stuck with
> macros for all those references forever, and they're not likely
> to change again any time soon. I don't think we'd really want
> to have macros for all our structure references on the off
> chance that someone might change it in the future.

Why? Macros (and inlined functions) have the advantage that they
enforce good policy. Doing 'task->cred->uid = a' on tasks other than
'current' is in general not a very safe thing to do. This sort of
issue w.r.t. safe policies should in particular be worrying you when
you start adding CRED_CLONE...
There are good precedents for this sort of argument: see
'set_current_state()' & friends.

In addition, those macros would allow you to set up compatibility with
2.4.x and simplify patch backports.

As for changing the structure: As I said previously I'd like to unify
all those { fsuid, fsgid, group } things into a proper ucred, so that
we can share these objects around the VFS, and cache them...
Your 'struct cred' as it stands will not suffice to do all that since
it does not provide the necessary Copy On Write protection. (For
instance if some thread temporarily raises my process privileges, I
will *not* want all my already opened 'struct file's to suddenly gain
root access).

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:27    [W:0.074 / U:1.692 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site