From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Linux-FSDevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC] POSIX ACL kernel infrastructure
Date: Mon, 5 Aug 2002 13:28:32 +0100 [thread overview]
Message-ID: <20020805132832.B5301@infradead.org> (raw)
In-Reply-To: <200208051411.33286.agruen@suse.de>; from agruen@suse.de on Mon, Aug 05, 2002 at 02:11:33PM +0200
On Mon, Aug 05, 2002 at 02:11:33PM +0200, Andreas Gruenbacher wrote:
> It was 2.4.10; I've canged that. I wanted to use identical code from 2.2 to
> 2.4; the non-2.5 parts can be stripped off.
Then strip them off :) especially as you added even more ugly checks around
the lock_kernel/unlock_kernel invocations..
> Using `struct posix_acl' everywhere is so much more messy.
Why?
> Is an exception
> justified here? The core kernel code has typedefs all over the place.
Ask Linus.. You should at least provide an alternate struct posix_acl
definition so fs.h doesn't have to pull in posix_acl.h but can use a
struct forward declaration.
> >From user space, yes. The get_posix_acl operation is currently used in nfsd;
> going via the xattr operations would be too expensive here. The set_posix_acl
> operation is indeed not used so far; I think it makes sense to add it for
> completeness' sake.
I'm not fully convienced. At least add the locking rules to Documentation/
filesystems/Locking. Documentation/filesystems/porting should also get a
an entry about the ACL support.
next prev parent reply other threads:[~2002-08-05 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 13:46 [RFC] POSIX ACL kernel infrastructure Andreas Gruenbacher
2002-08-04 14:04 ` Christoph Hellwig
2002-08-04 14:14 ` Andreas Gruenbacher
2002-08-04 14:33 ` Christoph Hellwig
2002-08-05 12:11 ` Andreas Gruenbacher
2002-08-05 12:28 ` Christoph Hellwig [this message]
2002-08-09 2:02 ` Nathan Scott
2002-08-09 10:53 ` Andreas Gruenbacher
2002-08-09 11:15 ` Christoph Hellwig
2002-08-09 12:22 ` Andreas Gruenbacher
2002-08-09 12:32 ` Christoph Hellwig
2002-08-09 13:17 ` Andreas Gruenbacher
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=20020805132832.B5301@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
/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