Re: [PATCH 4/7] allow killing tasks in your own or child userns

From: Serge E. Hallyn
Date: Mon Jan 10 2011 - 20:30:41 EST


Quoting Bastian Blank (bastian@xxxxxxxxxxxx):
> On Mon, Jan 10, 2011 at 04:51:51PM -0600, Serge Hallyn wrote:
> > Quoting Bastian Blank (bastian@xxxxxxxxxxxx):
> > > Isn't that equal to this?
> > >
> > > if (ns_capable(tcred->user->user_ns, CAP_KILL))
> > > return 1;
> > >
> > > if (cred->user->user_ns == tcred->user->user_ns &&
> > > (cred->euid == tcred->suid ||
> > > cred->euid == tcred->uid ||
> > > cred->uid == tcred->suid ||
> > > cred->uid == tcred->uid))
> > > return 1;
> > >
> > > return 0;
> > >
> > > I would consider this much easier to read.
> >
> > Unfortunately, it's actually not equivalent. when capable()
> > returns success, then it sets the current->flags |= PF_SUPERPRIV.
> > If permission is granted based on userids and the capability
> > isn't needed, then we don't want to needlessly set PF_SUPERPRIV.
>
> Well, then switch the two if-clauses.

hup, will do, much nicer, thanks.

> What is this flag used for anyway? I only see it used in the accounting
> stuff, and if every user can get it, it is not longer useful.

hm, I'm not sure... maybe noone is using it!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/