diff options
author | Brian Behlendorf <[email protected]> | 2011-06-30 09:38:52 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2011-07-01 13:39:48 -0700 |
commit | 285226eff39b807c154748a75cef57ddff08a352 (patch) | |
tree | b3f3c6340724727abe5f6957c74b4f0387bebad2 /module/zfs/zfs_vnops.c | |
parent | f2cfee80e3f94cd9d67c3f1abec97c9a5a5ecc17 (diff) |
Always allow non-user xattrs
Under Linux you may only disable USER xattrs. The SECURITY,
SYSTEM, and TRUSTED xattr namespaces must always be available
if xattrs are supported by the filesystem. The enforcement
of USER xattrs is performed in the zpl_xattr_user_* handlers.
Under Solaris there is only a single xattr namespace which
is managed globally.
Diffstat (limited to 'module/zfs/zfs_vnops.c')
-rw-r--r-- | module/zfs/zfs_vnops.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/module/zfs/zfs_vnops.c b/module/zfs/zfs_vnops.c index 828253f96..ae61b4304 100644 --- a/module/zfs/zfs_vnops.c +++ b/module/zfs/zfs_vnops.c @@ -1113,14 +1113,6 @@ zfs_lookup(struct inode *dip, char *nm, struct inode **ipp, int flags, if (flags & LOOKUP_XATTR) { /* - * If the xattr property is off, refuse the lookup request. - */ - if (!(zsb->z_flags & ZSB_XATTR)) { - ZFS_EXIT(zsb); - return (EINVAL); - } - - /* * We don't allow recursive attributes.. * Maybe someday we will. */ |