Re: [rfc] fcntl: Add F_GETOWNER_UIDS option
From: Oleg Nesterov
Date: Wed Mar 28 2012 - 17:39:50 EST
On 03/28, Serge Hallyn wrote:
> Quoting Oleg Nesterov (oleg@xxxxxxxxxx):
> > On 03/28, Serge E. Hallyn wrote:
> > >
> > > If you want to
> > > just add the struct cred to the f_owner and do proper uid conversion,
> > > I'll support that too. (Just grab a ref to the cred in
> > > fs/fcntl.c:f_modown(), and drop the ref in fs/file_table.c:__fput() ).
> > In this case f_owner.*uid should go away, I guess.
> Which I guess is all the more reason *not* to do this unless we end up
> not going with Eric's userns mapping patchset (which is unlikely).
> > And sigio_perm()
> > should be unified with kill_ok_by_cred() somehow (modulo
> > security_file_send_sigiotask).
> > Right?
> Maybe, but other differences include current being the signal sender in
> one and recipient in the other, and CAP_KILL being relevent in only
Yes, yes, sure. "current" is meaningless for sigio_perm().
That is why I asked, the "somehow" above is not clear to me.
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/