1. 14 11月, 2015 1 次提交
    • A
      9p: xattr simplifications · e409de99
      Andreas Gruenbacher 提交于
      Now that the xattr handler is passed to the xattr handler operations, we
      can use the same get and set operations for the user, trusted, and security
      xattr namespaces.  In those namespaces, we can access the full attribute
      name by "reattaching" the name prefix the vfs has skipped for us.  Add a
      xattr_full_name helper to make this obvious in the code.
      
      For the "system.posix_acl_access" and "system.posix_acl_default"
      attributes, handler->prefix is the full attribute name; the suffix is the
      empty string.
      Signed-off-by: NAndreas Gruenbacher <agruenba@redhat.com>
      Cc: Eric Van Hensbergen <ericvh@gmail.com>
      Cc: Ron Minnich <rminnich@sandia.gov>
      Cc: Latchesar Ionkov <lucho@ionkov.net>
      Cc: v9fs-developer@lists.sourceforge.net
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      e409de99
  2. 08 7月, 2013 1 次提交
    • J
      fs/9p: xattr: add trusted and security namespaces · d9a73859
      Jim Garlick 提交于
      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: NJim Garlick <garlick@llnl.gov>
      Signed-off-by: NEric Van Hensbergen <ericvh@gmail.com>
      d9a73859
  3. 26 2月, 2013 1 次提交
  4. 28 10月, 2010 2 次提交
  5. 03 8月, 2010 1 次提交