ubifs: Fix races between xattr_{set|get} and listxattr operations
authorZhihao Cheng <chengzhihao1@huawei.com>
Mon, 31 May 2021 12:52:09 +0000 (20:52 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 19 Jul 2021 07:45:00 +0000 (09:45 +0200)
commit38dde03eb239605f428f3f1e4baa73d4933a4cc6
tree7add4f298af1219c44c42184c8f5040584944f9a
parent690a11fb4e9f48caa3be21d408d48d08e7619033
ubifs: Fix races between xattr_{set|get} and listxattr operations

commit f4e3634a3b642225a530c292fdb1e8a4007507f5 upstream.

UBIFS may occur some problems with concurrent xattr_{set|get} and
listxattr operations, such as assertion failure, memory corruption,
stale xattr value[1].

Fix it by importing a new rw-lock in @ubifs_inode to serilize write
operations on xattr, concurrent read operations are still effective,
just like ext4.

[1] https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com

Fixes: 1e51764a3c2ac05a23 ("UBIFS: add new flash file system")
Cc: stable@vger.kernel.org # v2.6+
Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Reviewed-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ubifs/super.c
fs/ubifs/ubifs.h
fs/ubifs/xattr.c