mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-11 04:18:39 +08:00
0c3bc7899e
While looking at our current POSIX ACL handling in the context of some
overlayfs work I went through a range of other filesystems checking how they
handle them currently and encountered ntfs3.
The posic_acl_{from,to}_xattr() helpers always need to operate on the
filesystem idmapping. Since ntfs3 can only be mounted in the initial user
namespace the relevant idmapping is init_user_ns.
The posix_acl_{from,to}_xattr() helpers are concerned with translating between
the kernel internal struct posix_acl{_entry} and the uapi struct
posix_acl_xattr_{header,entry} and the kernel internal data structure is cached
filesystem wide.
Additional idmappings such as the caller's idmapping or the mount's idmapping
are handled higher up in the VFS. Individual filesystems usually do not need to
concern themselves with these.
The posix_acl_valid() helper is concerned with checking whether the values in
the kernel internal struct posix_acl can be represented in the filesystem's
idmapping. IOW, if they can be written to disk. So this helper too needs to
take the filesystem's idmapping.
Fixes:
|
||
|---|---|---|
| .. | ||
| lib | ||
| attrib.c | ||
| attrlist.c | ||
| bitfunc.c | ||
| bitmap.c | ||
| debug.h | ||
| dir.c | ||
| file.c | ||
| frecord.c | ||
| fslog.c | ||
| fsntfs.c | ||
| index.c | ||
| inode.c | ||
| Kconfig | ||
| lznt.c | ||
| Makefile | ||
| namei.c | ||
| ntfs_fs.h | ||
| ntfs.h | ||
| record.c | ||
| run.c | ||
| super.c | ||
| upcase.c | ||
| xattr.c | ||