linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux FSdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Dave McCracken <dmccr@us.ibm.com>
Subject: Re: [PATCH] Introduce BSD-style user credential [3/3]
Date: Fri, 30 Aug 2002 21:18:36 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0208302110280.1524-100000@home.transmeta.com> (raw)
In-Reply-To: <15728.7151.27079.551845@charged.uio.no>


On Sat, 31 Aug 2002, Trond Myklebust wrote:
> 
>   Add the COW structure 'vfs_cred'
> 
>   Make VFS changes to replace all instances of
>   current->fsuid/fsgid/ngroups/groups with a single 'vfs_cred' that
>   never can be changed by CLONE_CRED after we call down into the VFS.

Yup, I think I like that plan.

One thing that may be interesting (I certainly think it migth be), would
be to add a "struct user_struct *" pointer to the vfs_cred as well. This
is because I'd just _love_ to have that "user_struct" fed down to the VFS
layer, since I think that is where we may some day want to put things like
user-supplied cryptographic keys etc.

The advantage of "struct user_struct" (as opposed to just a uid_t) is that 
it can have information that lives for the whole duration of a login, and 
it's really the only kind of data structure in the kernel that can track 
that kind of information. 

>      > (I would suggest calling the FS credentials "struct vfs_cred",
>      > while the regular user credentials might just be "struct cred".
>      > Other suggestions?)
> 
> I'm fine about 'vfs_cred', but how about 'struct task_cred' instead
> for the second?

Sounds fine to me.

		Linus


  reply	other threads:[~2002-08-31  4:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-30 23:15 [PATCH] Introduce BSD-style user credential [3/3] Trond Myklebust
2002-08-30 23:40 ` Linus Torvalds
2002-08-31  0:24   ` Trond Myklebust
2002-08-31  0:49     ` Linus Torvalds
2002-08-31  0:51       ` Alan Cox
2002-08-31  0:56         ` Trond Myklebust
2002-08-31  1:01         ` Chris Wright
2002-08-31  1:04         ` Linus Torvalds
2002-08-31 16:13         ` Daniel Phillips
2002-08-31 16:43           ` Alan Cox
2002-08-31  1:29       ` Trond Myklebust
2002-08-31  4:18         ` Linus Torvalds [this message]
2002-08-31 12:02           ` Kai Henningsen
2002-08-31 16:30           ` Trond Myklebust
2002-09-01 15:23             ` Daniel Phillips
2002-08-31 19:06 ` Florian Weimer

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=Pine.LNX.4.44.0208302110280.1524-100000@home.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=dmccr@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).