From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] use generic ACL code
Date: Mon, 25 Feb 2008 09:09:30 +0100 [thread overview]
Message-ID: <200802250909.31170.agruen@suse.de> (raw)
In-Reply-To: <20080207083222.GA14317@lst.de>
On Thursday 07 February 2008 09:32:22 Christoph Hellwig wrote:
> This also introduces the same ACL caching all other Linux filesystems do
> by adding pointers to the acl and default acl in struct xfs_inode.
> It'll probably need some benchmarking to find out whether bloating the
> inode is worth it.
I guess it all depends on the workload.
> It should be possible to use the generic code without this caching by
> revamping the code a little, although no other filesystem currently does
> that.
The options for doing that would be (a) basically what xfs does now, i.e.,
perform the permission checks directly in the on-disk data, or (b) construct
struct posix_acl objects temporarily for each access. Option (b) doesn't look
very appealing to me.
> + * XXX(hch): the tag is 32 bits on disk and 16 bits in core.
> + * Any special handling required??
> + */
> + acl_e->e_tag = be32_to_cpu(ace->ae_tag);
> + acl_e->e_perm = be16_to_cpu(ace->ae_perm);
I would check for zero upper bits on disk.
Thanks,
Andreas
prev parent reply other threads:[~2008-02-25 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 8:32 [PATCH, RFC] use generic ACL code Christoph Hellwig
2008-02-08 3:25 ` Timothy Shimmin
2008-02-14 4:43 ` Timothy Shimmin
2008-02-16 7:19 ` Christoph Hellwig
2008-02-25 8:09 ` Andreas Gruenbacher [this message]
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=200802250909.31170.agruen@suse.de \
--to=agruen@suse.de \
--cc=hch@lst.de \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox