mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems with changing UID/GID
Date: Wed, 28 Aug 2002 09:24:23 -0500	[thread overview]
Message-ID: <19220000.1030544663@baldur.austin.ibm.com> (raw)
In-Reply-To: <200208280009.03090.trond.myklebust@fys.uio.no>


--On Wednesday, August 28, 2002 12:09:03 AM +0200 Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:

> FYI a BSD ucred is basically a structure of the form
> 
> struct ucred {
> 	int	counter;		/* Reference counter */
> 	uid_t	uid;			/* task->fsuid */
> 	gid_t	gid;			/* task->fsgid */
> 	int	ngroups;		/* task->ngroups */
> 	gid_t	*groups;		/* task->groups */
> };

Shouldn't the Linux cred structure include the capabilities, as well?  What
about places that want to see both uid and euid?  Shouldn't euid/egid also
be in the structure?  I realize that for file operations they're not
strictly necessary, but we should make the structure useful across all
parts of the kernel that want to see credentials.

BTW, you've convinced me that your approach is the right way to go.  I'll
make another stab at CLONE_CRED after the VFS changes are made, which will
make it a 2.7 item, I'm sure.

Dave McCracken

======================================================================
Dave McCracken          IBM Linux Base Kernel Team      1-512-838-3059
dmccr@us.ibm.com                                        T/L   678-3059


  reply	other threads:[~2002-08-28 14:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 13:30 Zheng Jian-Ming
2002-08-26 13:45 ` Alan Cox
2002-08-27 21:21   ` Mike Touloumtzis
2002-08-28 11:51   ` Florian Weimer
2002-08-28 14:01     ` Alan Cox
2002-08-26 14:58 ` Thunder from the hill
2002-08-26 17:16   ` Alan Cox
2002-08-26 17:31     ` Thunder from the hill
2002-08-26 18:47     ` Trond Myklebust
2002-08-26 18:49     ` Luca Barbieri
2002-08-27  7:54     ` Chris Wedgwood
2002-08-27 15:42       ` Thunder from the hill
2002-08-27 18:12         ` Chris Wedgwood
2002-08-27 19:08           ` Thunder from the hill
2002-08-27 20:00             ` Chris Wedgwood
2002-08-27 20:25               ` Thunder from the hill
2002-08-27 20:52                 ` Chris Wedgwood
2002-08-27 19:35       ` Trond Myklebust
2002-08-27 20:01         ` Chris Wedgwood
2002-08-27 22:09           ` Trond Myklebust
2002-08-28 14:24             ` Dave McCracken [this message]
2002-08-28 18:30               ` Trond Myklebust
2002-08-28 20:59                 ` Dave McCracken
2002-08-28 23:20                   ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19220000.1030544663@baldur.austin.ibm.com \
    --to=dmccr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®