From: kaih@khms.westfalen.de (Kai Henningsen)
To: torvalds@transmeta.com
Cc: linux-fsdevel@vger.kernel.org
Cc: dmccr@us.ibm.com
Cc: linux-kernel@vger.kernel.org
Cc: trond.myklebust@fys.uio.no
Subject: Re: [PATCH] Introduce BSD-style user credential [3/3]
Date: 31 Aug 2002 14:02:00 +0200 [thread overview]
Message-ID: <8Vuk51-mw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0208302110280.1524-100000@home.transmeta.com>
torvalds@transmeta.com (Linus Torvalds) wrote on 30.08.02 in <Pine.LNX.4.44.0208302110280.1524-100000@home.transmeta.com>:
> 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.
In that case, wouldn't "struct session" be a better name?
MfG Kai
next prev parent reply other threads:[~2002-08-31 12:02 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 [this message]
2002-08-31 16:30 ` Trond Myklebust
2002-09-01 15:23 ` Daniel Phillips
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=8Vuk51-mw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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