public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: ACL limit
Date: Mon, 03 Dec 2007 10:47:07 +1100	[thread overview]
Message-ID: <475343FB.3060902@sgi.com> (raw)
In-Reply-To: <20071202223105.GS119954183@sgi.com>

David Chinner wrote:
> On Fri, Nov 30, 2007 at 07:07:26PM +0100, Jan Engelhardt wrote:
>> Hi,
>>
>>
>> is there any way to raise the number of ACLs that can be stored? The 
>> current limit of 25 is quite tight, where ext3 allows 124 and jfs 8192.
>> Would increasing XFS_ACL_MAX_ENTRIES work (yes, using potentially more 
>> memory), i.e. not interfering with the on-disk format?
> 
> It would be an on disk format change - older kernels would error out
> (-EINVAL) on > 25 ACLs and not check any of them. Hence we'd
> probably need a superblock feature bit to indicate that >25 ACEs are
> supported in a given ACL.
> 
> But we can work around that (superblock feature bit) and should
> be able to extend this out to ~8190 entries. We're doing an ACL
> rework ATM, so > 25 entry support should fall out of that....
> 
> Cheers,
> 
> Dave.

Yeah, it's just an array of entries in an EA value.
The EA value is limited to 64K so it's a question of how
many entries you can fit into that.
(64K - 4)/12 = 5461

(So just have to sort out the ondisk change as mentioned above)

--Tim

  reply	other threads:[~2007-12-02 23:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 18:07 ACL limit Jan Engelhardt
2007-12-02 22:31 ` David Chinner
2007-12-02 23:47   ` Timothy Shimmin [this message]
2007-12-03  0:12     ` Jan Engelhardt
2007-12-03  0:23     ` David Chinner
2007-12-03  0:34       ` Timothy Shimmin

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=475343FB.3060902@sgi.com \
    --to=tes@sgi.com \
    --cc=dgc@sgi.com \
    --cc=jengelh@computergmbh.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