From: Haowen Bai <baihaowen@meizu.com>
Date: Tue, 22 Mar 2022 10:13:04 +0000 (+0800)
Subject: ubifs: Use NULL instead of using plain integer as pointer
X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=532aef5912c2c2add9ae725bcb1d0924e609dd87;p=linux.git

ubifs: Use NULL instead of using plain integer as pointer

This fixes the following sparse warnings:
fs/ubifs/xattr.c:680:58: warning: Using plain integer as NULL pointer

Signed-off-by: Haowen Bai <baihaowen@meizu.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
---

diff --git a/fs/ubifs/xattr.c b/fs/ubifs/xattr.c
index e4f193eae4b2b..e4c4761aff7f8 100644
--- a/fs/ubifs/xattr.c
+++ b/fs/ubifs/xattr.c
@@ -677,7 +677,7 @@ int ubifs_init_security(struct inode *dentry, struct inode *inode,
 	int err;
 
 	err = security_inode_init_security(inode, dentry, qstr,
-					   &init_xattrs, 0);
+					   &init_xattrs, NULL);
 	if (err) {
 		struct ubifs_info *c = dentry->i_sb->s_fs_info;
 		ubifs_err(c, "cannot initialize security for inode %lu, error %d",