mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Filipe David Borba Manana
8bab8b31bb
This test is motivated by an issue found by a btrfs user, addressed and described by the following Linux kernel patch: https://patchwork.kernel.org/patch/3046931/ The steps to reproduce the issue on btrfs are the following: $ mkfs.btrfs -f /dev/loop0 $ mount /dev/loop0 /mnt $ mkdir /mnt/acl $ setfacl -d --set u::rwx,g::rwx,o::- /mnt/acl $ getfacl /mnt/acl user::rwx group::rwx other::r-x default:user::rwx default:group::rwx default:other::--- $ mkdir /mnt/acl/dir1 $ getfacl /mnt/acl/dir1 user::rwx group::rwx other::--- After unmounting and mounting again the filesystem, getfacl returned the expected default ACL for the subdirectory: $ umount /mnt/acl $ mount /dev/loop0 /mnt $ getfacl /mnt/acl/dir1 user::rwx group::rwx other::--- default:user::rwx default:group::rwx default:other::--- This means that the underlying ACL xattr was persisted correctly but the in memory representation of the inode had (incorrectly) a NULL ACL. [rjohnston: renumbered test to 319] Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> Reviewed-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Rich Johnston <rjohnston@sgi.com>
22 lines
326 B
Plaintext
22 lines
326 B
Plaintext
QA output created by 319
|
|
# file: SCRATCH_MNT/testdir
|
|
# owner: root
|
|
# group: root
|
|
user::rwx
|
|
group::r-x
|
|
other::r-x
|
|
default:user::rwx
|
|
default:group::rwx
|
|
default:other::---
|
|
|
|
# file: SCRATCH_MNT/testdir/testsubdir
|
|
# owner: root
|
|
# group: root
|
|
user::rwx
|
|
group::rwx
|
|
other::---
|
|
default:user::rwx
|
|
default:group::rwx
|
|
default:other::---
|
|
|