Lets have another root owned file but this time one that is
world writable:

islay:pts/4$ ls -l
total 0
-rw-r--r--   1 darrenm  staff          0 Aug  7 15:34 test1
-rw-r--r--   1 darrenm  root           0 Aug  7 15:35 test2
-rw-rw-rw-   1 root     root           0 Aug  7 15:35 test3
islay:pts/4$ runat test3 cp /tmp/attrdata attr.1
cp[1799]: missing privilege "ALL" (euid = 35661, syscall = 224) needed at ufs_iaccess+0xf8
cp: cannot create attr.1: Permission denied

Hmn, slightly strange since I would have thought that given write
to the file I could write attributes.  ZFS is consistent in this
because the default ZFS ACL does not have everyone@ having write_xattr. Maybe not quite what one would expect.


Whats happening is that when you change the mode or owner of the base file the mode and owner of the hidden directory aren't changing. With UFS the mode of the hidden directory is created when the attribute directory is initially created. When the mode or owner of the base file is changed the corresponding mode/owner of the hidden attribute directory are not updated as well.

This is slightly different in ZFS because it actually has real permissions for xattr's. Also, when the owner/group of the base file is changed the owner/group of the hidden directory is also updated.

Okay now in another window change the ownership of this world writable
file to darrenm

islay:pts/4$ runat test3 cp /tmp/attrdata attr.1
cp[1802]: missing privilege "ALL" (euid = 35661, syscall = 224) needed at ufs_iaccess+0xf8
cp: cannot create attr.1: Permission denied
islay:pts/4$ ls -l
total 0
-rw-r--r--   1 darrenm  staff          0 Aug  7 15:34 test1
-rw-r--r--   1 darrenm  root           0 Aug  7 15:35 test2
-rw-rw-rw-   1 darrenm  staff          0 Aug  7 15:35 test3

Hmn very strange.  On UFS this is still failing as if it were a
root owned file.  On ZFS this case works as expected.

The UFS behaviour is clearly a bug, the default ZFS behaviour of not allowing the creation of attributes by anyone other than the actual owner (at least by default) maybe a little confusing but I'm not too bothered about that.

TMPFS has the same behaviour as UFS with respect to the problem around when the chown is done.


_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to