From: Daniel Phillips <phillips@arcor.de>
To: trond.myklebust@fys.uio.no, Linus Torvalds <torvalds@transmeta.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
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: Sun, 1 Sep 2002 17:23:57 +0200 [thread overview]
Message-ID: <E17lWZy-0004Zm-00@starship> (raw)
In-Reply-To: <15728.61204.381468.238609@charged.uio.no>
On Saturday 31 August 2002 18:30, Trond Myklebust wrote:
> >>>>> " " == Linus Torvalds <torvalds@transmeta.com> writes:
>
> > 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.
>
> No problem at all with this. Indeed I agree it makes a lot of sense...
>
> The only thing is if you'd allow me to do it as an incremental patch
> to the initial one?
> I don't see 'struct user_struct *' as replacing the existing 'uid'
> entry, so there should be no need to change the existing API. Instead,
> we can just add in the necessary call to alloc_uid() to
> vfscred_create() and/or setfsuid()...
I really do like Kai's name suggestion 'struct session'.
--
Daniel
next prev parent reply other threads:[~2002-09-01 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15727.64653.78081.277222@charged.uio.no>
2002-08-30 23:40 ` [PATCH] Introduce BSD-style user credential [3/3] Linus Torvalds
2002-08-31 0:24 ` Trond Myklebust
2002-08-31 0:49 ` Linus Torvalds
[not found] ` <Pine.LNX.4.44.0208301741430.5561-100000@home.transmeta.com>
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
2002-08-31 12:02 ` Kai Henningsen
2002-08-31 16:30 ` Trond Myklebust
2002-09-01 15:23 ` Daniel Phillips [this message]
2002-08-30 23:15 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=E17lWZy-0004Zm-00@starship \
--to=phillips@arcor.de \
--cc=dmccr@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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