08 Jul, 2013
1 commit
-
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=95Signed-off-by: Jim Garlick
Signed-off-by: Eric Van Hensbergen
22 Jan, 2013
1 commit
-
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.CC: Eric Van Hensbergen
CC: Ron Minnich
CC: Latchesar Ionkov
Cc: Al Viro
Signed-off-by: Kees Cook
Signed-off-by: Greg Kroah-Hartman
25 May, 2011
1 commit
-
The 9p client is currently undergoing regular regresssion and
stress testing as a by-product of the virtfs work. I think its
finally time to take off the experimental tags from the well-tested
code paths.Signed-off-by: Eric Van Hensbergen
11 Jan, 2011
1 commit
-
Make the 9P_FS kconfig options subordinate to the 9P_FS kconfig symbol
in the menu presentation instead of them all being at the same level.Signed-off-by: Randy Dunlap
Signed-off-by: Eric Van Hensbergen
28 Oct, 2010
1 commit
-
The ACL value is fetched as a part of inode initialization
from the server and the permission checking function use the
cached value of the ACLSigned-off-by: Aneesh Kumar K.V
Signed-off-by: Venkateswararao Jujjuri
Signed-off-by: Eric Van Hensbergen
24 Sep, 2009
1 commit
-
This patch adds a persistent, read-only caching facility for
9p clients using the FS-Cache caching backend.When the fscache facility is enabled, each inode is associated
with a corresponding vcookie which is an index into the FS-Cache
indexing tree. The FS-Cache indexing tree is indexed at 3 levels:
- session object associated with each mount.
- inode/vcookie
- actual data (pages)A cache tag is chosen randomly for each session. These tags can
be read off /sys/fs/9p/caches and can be passed as a mount-time
parameter to re-attach to the specified caching session.Signed-off-by: Abhishek Kulkarni
Signed-off-by: Eric Van Hensbergen
22 Jan, 2009
1 commit
-
Signed-off-by: Alexey Dobriyan