[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181119033241.20264-1-yuehaibing@huawei.com>
Date: Mon, 19 Nov 2018 11:32:41 +0800
From: YueHaibing <yuehaibing@...wei.com>
To: <mszeredi@...hat.com>, <amir73il@...il.com>, <neilb@...e.com>,
<bfields@...hat.com>, <viro@...iv.linux.org.uk>
CC: <linux-kernel@...r.kernel.org>, <akpm@...ux-foundation.org>,
<matt.helsley@...il.com>, YueHaibing <yuehaibing@...wei.com>
Subject: [PATCH -next] exportfs: fix 'passing zero to ERR_PTR()' warning
Fix a static code checker warning:
fs/exportfs/expfs.c:171 reconnect_one() warn: passing zero to 'ERR_PTR'
The error path for lookup_one_len_unlocked failure
should set err to PTR_ERR.
Fixes: bbf7a8a3562f ("exportfs: move most of reconnect_path to helper function")
Signed-off-by: YueHaibing <yuehaibing@...wei.com>
---
fs/exportfs/expfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
index 645158d..c8a3dfd 100644
--- a/fs/exportfs/expfs.c
+++ b/fs/exportfs/expfs.c
@@ -147,6 +147,7 @@ static struct dentry *reconnect_one(struct vfsmount *mnt,
tmp = lookup_one_len_unlocked(nbuf, parent, strlen(nbuf));
if (IS_ERR(tmp)) {
dprintk("%s: lookup failed: %d\n", __func__, PTR_ERR(tmp));
+ err = PTR_ERR(tmp);
goto out_err;
}
if (tmp != dentry) {
--
2.7.0
Powered by blists - more mailing lists