summaryrefslogtreecommitdiffstats
path: root/fs/9p/xattr_user.c
diff options
context:
space:
mode:
authorAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>2010-05-31 09:52:50 +0200
committerEric Van Hensbergen <ericvh@gmail.com>2010-08-02 21:28:34 +0200
commiteda25e46161527845572131b37706a458d9270ef (patch)
treeb8a68c9185f7f53a135422a41dc68ef2c5f527ee /fs/9p/xattr_user.c
parentnet/9p: Implement attrwalk 9p call (diff)
downloadlinux-eda25e46161527845572131b37706a458d9270ef.tar.xz
linux-eda25e46161527845572131b37706a458d9270ef.zip
net/9p: Implement TXATTRCREATE 9p call
TXATTRCREATE: Prepare a fid for setting xattr value on a file system object. size[4] TXATTRCREATE tag[2] fid[4] name[s] attr_size[8] flags[4] size[4] RXATTRCREATE tag[2] txattrcreate gets a fid pointing to xattr. This fid can later be used to set the xattr value. flag value is derived from set Linux setxattr. The manpage says "The flags parameter can be used to refine the semantics of the operation. XATTR_CREATE specifies a pure create, which fails if the named attribute exists already. XATTR_REPLACE specifies a pure replace operation, which fails if the named attribute does not already exist. By default (no flags), the extended attribute will be created if need be, or will simply replace the value if the attribute exists." The actual setxattr operation happens when the fid is clunked. At that point the written byte count and the attr_size specified in TXATTRCREATE should be same otherwise an error will be returned. Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com> Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
Diffstat (limited to 'fs/9p/xattr_user.c')
0 files changed, 0 insertions, 0 deletions