On Fri, 24 Feb 2017 16:18:38 +0100
Anton Gerasimov wrote:
> FIG_FS_POSIX_ACL=y;
> CONFIG_EXT4_FS_POSIX_ACL=y). The problem is that 'cp -a' when copying
> a directory without any ACLs attached will for whatever reason try to
> assign an empty posix_acl_default list to the target directory.
...
I
On Fri, 24 Feb 2017 15:48:15 +0100
an...@advancedtelematic.com wrote:
> From: Anton Gerasimov
>
> The difference between what we see in pseudo and what happens without
> pseudo can be seen by typing:
>
> mkdir setfattr-test
> setfattr -n system.posix_acl_default -v 0x0200 setfattr-t
From: Anton Gerasimov
The difference between what we see in pseudo and what happens without
pseudo can be seen by typing:
mkdir setfattr-test
setfattr -n system.posix_acl_default -v 0x0200 setfattr-test
getfattr -n system.posix_acl_default setfattr-test
Under some kernel configu
Hi Peter,
to reproduce the difference, you just need a kernel with POSIX ACL
enabled for your FS (e.g. CONFIG_FS_POSIX_ACL=y;
CONFIG_EXT4_FS_POSIX_ACL=y). The problem is that 'cp -a' when copying a
directory without any ACLs attached will for whatever reason try to
assign an empty posix_acl_defaul
From: Anton Gerasimov
The difference between what we see in pseudo and what happens without
pseudo can be seen by typing:
mkdir setfattr-test
setfattr -n system.posix_acl_default -v 0x0200 setfattr-test
getfattr -n system.posix_acl_default setfattr-test
Under some kernel configu
