d9a738597f
Allow requests for security.* and trusted.* xattr name spaces to pass through to server. The new files are 99% cut and paste from fs/9p/xattr_user.c with the namespaces changed. It has the intended effect in superficial testing. I do not know much detail about how these namespaces are used, but passing them through to the server, which can decide whether to handle them or not, seems reasonable. I want to support a use case where an ext4 file system is mounted via 9P, then re-exported via samba to windows clients in a cluster. Windows wants to store xattrs such as security.NTACL. This works when ext4 directly backs samba, but not when 9P is inserted. This use case is documented here: http://code.google.com/p/diod/issues/detail?id=95 Signed-off-by: Jim Garlick <garlick@llnl.gov> Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
20 lines
335 B
Makefile
20 lines
335 B
Makefile
obj-$(CONFIG_9P_FS) := 9p.o
|
|
|
|
9p-objs := \
|
|
vfs_super.o \
|
|
vfs_inode.o \
|
|
vfs_inode_dotl.o \
|
|
vfs_addr.o \
|
|
vfs_file.o \
|
|
vfs_dir.o \
|
|
vfs_dentry.o \
|
|
v9fs.o \
|
|
fid.o \
|
|
xattr.o \
|
|
xattr_user.o \
|
|
xattr_trusted.o
|
|
|
|
9p-$(CONFIG_9P_FSCACHE) += cache.o
|
|
9p-$(CONFIG_9P_FS_POSIX_ACL) += acl.o
|
|
9p-$(CONFIG_9P_FS_SECURITY) += xattr_security.o
|