Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
xfs: allow 2048 acl entries per inode (XFS_ACL_MAX_ENTRIES)
We need to keep in mind the following: - In V5-superblock, XFS allows to have up to 64KB of xattr data, which is about 5400 ACLs, so our value is still less than that. See: commit 0a8aa1939777dd114479677f0044652c1fd72398 xfs: increase number of ACL entries for V5 superblocks http://oss.sgi.com/archives/xfs/2013-06/msg00020.html - commit 2dc164f2965b92a6efd2edb9e2813271741e96db (xfs: fix memory allocation failures with ACLs) uses vmalloc to allocate large buffers for ACLs. In our commit, we also use vzalloc instead of kzalloc. However, note the comments in kmem_zalloc_large() of the mainline code. - We change XFS_ACL_MAX_ENTRIES without changing the superblock version. This is alright for us, as long as we never downgrade VPSA version (which we should never ever do). - struct xfs_acl_entry in our code does not have the "ae_pad" field (which it has upstream), but the size of the structure is (somehow) still the same (12 bytes) DDF4624D7A2FF62052FC99E
- Loading branch information
1 parent
21dc2e0
commit 094df94
Showing
5 changed files
with
169 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.