ubifs: Massage assert in ubifs_xattr_set() wrt. fscrypto



When we're creating a new inode in UBIFS the inode is not
yet exposed and fscrypto calls ubifs_xattr_set() without
holding the inode mutex. This is okay but ubifs_xattr_set()
has to know about this.

Signed-off-by: Richard Weinberger <richard@nod.at>

parent 9270b2f4

fs/ubifs/xattr.c

+7 −1

Original line number	Diff line number	Diff line
		@@ -289,6 +289,12 @@ int ubifs_xattr_set(struct inode host, const char name, const void *value,
		union ubifs_key key;
		int err;

		/*
		* Creating an encryption context is done unlocked since we
		* operate on a new inode which is not visible to other users
		* at this point.
		*/
		if (strcmp(name, UBIFS_XATTR_NAME_ENCRYPTION_CONTEXT) != 0)
		ubifs_assert(inode_is_locked(host));

		if (size > UBIFS_MAX_INO_DATA)