All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Nathan Scott <nathans@sgi.com>,
	Christoph Hellwig <hch@infradead.org>,
	Linux-FSDevel <linux-fsdevel@vger.kernel.org>,
	Olaf Kirch <okir@suse.de>, Chris Mason <mason@suse.de>,
	Jeff Mahoney <jeffm@suse.com>
Subject: Re: [RFC] POSIX ACL kernel infrastructure
Date: Fri, 9 Aug 2002 12:15:02 +0100	[thread overview]
Message-ID: <20020809121502.A8178@infradead.org> (raw)
In-Reply-To: <200208091253.55935.agruen@suse.de>; from agruen@suse.de on Fri, Aug 09, 2002 at 12:53:55PM +0200

On Fri, Aug 09, 2002 at 12:53:55PM +0200, Andreas Gruenbacher wrote:
> The kernel NFS daemon introduces a number of interesting problems in the 
> kernel that no other component requires; the ACL permission masking hack is 
> one of them. The hack affects NFSv2 and NFSv3 
> 
> It is really important that encode_fattr and encode_fattr3, the functions that 
> include the hack, are efficient; they are used in all the essential NFS RPCs.

IF it's so essential why are you doing another IOP call then instead of adding
inkernel A retrieving to ->getattr and struct kstat?  encode_fattr* has to
call it anyway and that's the logical place for ACLs..


  reply	other threads:[~2002-08-09 11:15 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
2002-08-09  2:02           ` Nathan Scott
2002-08-09 10:53             ` Andreas Gruenbacher
2002-08-09 11:15               ` Christoph Hellwig [this message]
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=20020809121502.A8178@infradead.org \
    --to=hch@infradead.org \
    --cc=agruen@suse.de \
    --cc=jeffm@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mason@suse.de \
    --cc=nathans@sgi.com \
    --cc=okir@suse.de \
    /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.