summaryrefslogtreecommitdiffstats
path: root/net/9p
diff options
context:
space:
mode:
authorpiaojun <piaojun@huawei.com>2018-07-25 11:13:16 +0800
committerDominique Martinet <dominique.martinet@cea.fr>2018-08-13 09:35:16 +0900
commit3111784bee81591ea2815011688d28b65df03627 (patch)
tree049732d6fcb3828679f712e35305d4d3752bd374 /net/9p
parentf984579a01d85166ee7380204a96d978a67687a1 (diff)
downloadlinux-3111784bee81591ea2815011688d28b65df03627.tar.bz2
fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr failed
In my testing, v9fs_fid_xattr_set will return successfully even if the backend ext4 filesystem has no space to store xattr key-value. That will cause inconsistent behavior between front end and back end. The reason is that lsetxattr will be triggered by p9_client_clunk, and unfortunately we did not catch the error. This patch will catch the error to notify upper caller. p9_client_clunk (in 9p) p9_client_rpc(clnt, P9_TCLUNK, "d", fid->fid); v9fs_clunk (in qemu) put_fid free_fid v9fs_xattr_fid_clunk v9fs_co_lsetxattr s->ops->lsetxattr ext4_xattr_user_set (in host ext4 filesystem) Link: http://lkml.kernel.org/r/5B57EACC.2060900@huawei.com Signed-off-by: Jun Piao <piaojun@huawei.com> Cc: Eric Van Hensbergen <ericvh@gmail.com> Cc: Ron Minnich <rminnich@sandia.gov> Cc: Latchesar Ionkov <lucho@ionkov.net> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: stable@vger.kernel.org Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
Diffstat (limited to 'net/9p')
0 files changed, 0 insertions, 0 deletions