From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: David Howells <dhowells@warthog.cambridge.redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
openafs-devel@openafs.org
Subject: Re: [PATCH] PAG support, try #2
Date: 18 May 2003 16:51:27 +0200 [thread overview]
Message-ID: <shs8yt4l34g.fsf@charged.uio.no> (raw)
In-Reply-To: <20030515131825.G672@nightmaster.csn.tu-chemnitz.de>
>>>>> " " == Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de> writes:
> On Wed, May 14, 2003 at 06:37:00PM +0100, David Howells wrote:
>> And then you have to have some method of prioritisation. You
>> may find that user dhowells has a token for
>> (fs=AFS,cell=redhat.com) and group engineering has a token for
>> (fs=AFS,cell=redhat.com). Which do you use?
> Union of both. And remember to subtract negative ACLs from
> positive ACLs. Prioritize users over groups in case of explicit
> mention.
> This is standard permission checking.
> Hmm, sounds too simple, so it must be wrong ;-)
Quite. Now that you've done the math, please explain how this should
be implemented efficiently. These are *networked* filesystems...
Cheers,
Trond
next prev parent reply other threads:[~2003-05-18 14:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 10:43 [PATCH] PAG support, try #2 David Howells
2003-05-14 10:56 ` Christoph Hellwig
2003-05-14 11:56 ` David Howells
2003-05-14 12:35 ` Christoph Hellwig
2003-05-14 12:45 ` William Lee Irwin III
2003-05-14 12:57 ` Jeff Garzik
2003-05-14 11:49 ` Matthew Wilcox
2003-05-14 12:03 ` David Howells
2003-05-14 16:49 ` Linus Torvalds
2003-05-14 17:37 ` David Howells
2003-05-15 11:18 ` Ingo Oeser
2003-05-18 14:51 ` Trond Myklebust [this message]
2003-05-14 19:28 ` H. Peter Anvin
2003-05-14 16:58 ` Jan Harkes
2003-05-14 17:11 ` Jan Harkes
2003-05-14 20:45 ` [OpenAFS-devel] " Harald Barth
2003-05-15 0:14 ` Garance A Drosihn
2003-05-15 0:14 ` Garance A Drosihn
2003-05-15 0:57 ` [OpenAFS-devel] " Linus Torvalds
2003-05-15 1:34 ` Trond Myklebust
2003-05-15 2:30 ` Linus Torvalds
2003-05-15 14:04 ` Dean Anderson
2003-05-15 16:20 ` Linus Torvalds
2003-05-15 16:41 ` David Howells
2003-05-15 17:23 ` Linus Torvalds
2003-05-16 12:12 ` David Howells
2003-05-15 23:00 ` Garance A Drosihn
2003-05-15 23:00 ` Garance A Drosihn
2003-05-15 23:21 ` QM_MODULES Function not implemented John Shillinglaw
2003-05-16 0:53 ` [OpenAFS-devel] Re: [PATCH] PAG support, try #2 Nathan Neulinger
2003-05-15 4:26 ` Russ Allbery
2003-05-15 4:26 ` Russ Allbery
2003-05-15 4:59 ` [OpenAFS-devel] " Linus Torvalds
2003-05-15 15:34 ` Booker Bense
2003-05-15 15:34 ` Booker Bense
2003-05-15 6:04 ` Riley Williams
2003-05-15 13:26 ` [OpenAFS-devel] " Garance A Drosihn
2003-05-15 13:26 ` Garance A Drosihn
2003-05-15 13:12 ` [OpenAFS-devel] " Garance A Drosihn
2003-05-15 13:12 ` Garance A Drosihn
2003-05-15 15:55 ` [OpenAFS-devel] " Douglas E. Engert
2003-05-15 15:55 ` Douglas E. Engert
2003-05-15 13:35 ` [OpenAFS-devel] " David Howells
2003-05-15 13:55 ` chas williams
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=shs8yt4l34g.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=dhowells@redhat.com \
--cc=dhowells@warthog.cambridge.redhat.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-devel@openafs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.