From: "David C. Hansen" <haveblue@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Dave McCracken <dmccr@us.ibm.com>
Subject: [RFC] shared credentials with vfs snapshotting
Date: 24 Oct 2002 13:12:40 -0700 [thread overview]
Message-ID: <1035490360.9081.73.camel@nighthawk> (raw)
This patch combines the ideas from two others: Dave McCracken's
combination of task credentials into a single structure which is
shared between threads:
http://marc.theaimsgroup.com/?t=102830918300009&r=1&w=2
And Trond Myklebust's snapshotting of the vfs-specific parts of
the cred structure which are passed down into vfs and are strictly
copy-on-write.
http://marc.theaimsgroup.com/?t=103081191900001&r=1&w=2
http://marc.theaimsgroup.com/?t=103074984200004&r=1&w=2
http://www.fys.uio.no/~trondmy/src/2.5.32-alpha
Implementing the appearance of shared credentials to userspace requires
large amounts of code to be added in the threading libraries. The
addition of code here is reasonalbly small.
This patch is by no means complete or correct. It completely ignores
the credential sharing flag for now. It is just here to demonstrate the
combination of the two ideas. Please don't go applying it to anything
;)
I think that the core of what is needed is in the attached patch. Most
of what is left can be accomplished with s/->uid/->cred->uid/ and
s/->fsuid/->cred->vfscred->uid/
And, as Trond says:
> Unfortunately there's still a bit more to do. I need to get
> the file creation ops (i_op->create()/symlink()/mknod()/mkdir()) to
> take a vfs_cred* argument. If not, you risk having the
> inode->i_uid/i_gid set to values that differ from the ones checked by
> the calls to ->permission().
--
Dave Hansen
haveblue@us.ibm.com
next reply other threads:[~2002-10-24 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 20:12 David C. Hansen [this message]
2002-10-24 20:24 ` [RFC] shared credentials with vfs snapshotting David C. Hansen
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=1035490360.9081.73.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=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