public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Robert Love <rml@tech9.net>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] (resend) credentials for 2.5.23
Date: 21 Jun 2002 13:12:59 +0200	[thread overview]
Message-ID: <shs4rfwx4uc.fsf@charged.uio.no> (raw)
In-Reply-To: <1024593066.922.149.camel@sinai>

>>>>> " " == Robert Love <rml@tech9.net> writes:

     > CLONE_CRED.  I suspect 90% of the cases retain the same
     > credentials anyhow.  Copy-on-write? :)

Ben,

  Making the credentials a monolithic block like you appear to be
doing just doesn't make sense. If you look at the way things like
fsuid/fsgid/groups[] are used, you will see that almost all those that
filesystems that care are making their own private copies.

  It would be a lot more useful to split out fsuid/fsgid/groups[] as
per the *BSD ucred, and then allow filesystems to reference the
resulting struct instead (using COW semantics).

That way too, 'struct file' could finally contain a reference to a
full copy of the filesystem credentials, and we could get rid of
the 'struct file' crud in address_space_operations like readpage().

See
  http://www.fys.uio.no/~trondmy/src/bsdcred/linux-2.5.1-pre11_cred.dif

for my earlier attempt at doing this sort of thing...

Cheers,
  Trond

  reply	other threads:[~2002-06-21 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  1:29 [patch] (resend) credentials for 2.5.23 Benjamin LaHaise
2002-06-20  2:30 ` Robert Love
2002-06-20 16:28   ` Benjamin LaHaise
2002-06-20 17:11     ` Robert Love
2002-06-21 11:12       ` Trond Myklebust [this message]
2002-06-21 18:52         ` Benjamin LaHaise
2002-06-21 19:17           ` 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=shs4rfwx4uc.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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