[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <514e5e4b-e7c8-365f-8459-75974c067993@huawei.com>
Date: Mon, 22 Aug 2022 19:46:07 +0800
From: Zhiqiang Liu <liuzhiqiang26@...wei.com>
To: "Darrick J. Wong" <djwong@...nel.org>, <linux-xfs@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: linfeilong <linfeilong@...wei.com>,
wuguanghao <wuguanghao3@...wei.com>, <liuzhiqiang26@...wei.com>
Subject: [PATCH] xfs: donot need to check return value of xlog_kvmalloc()
In xfs_attri_log_nameval_alloc(), xlog_kvmalloc() is called
to alloc memory, which will always return
successfully, so we donot need to check return value.
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@...wei.com>
---
fs/xfs/xfs_attr_item.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/xfs/xfs_attr_item.c b/fs/xfs/xfs_attr_item.c
index 5077a7ad5646..667e151a2bca 100644
--- a/fs/xfs/xfs_attr_item.c
+++ b/fs/xfs/xfs_attr_item.c
@@ -86,8 +86,6 @@ xfs_attri_log_nameval_alloc(
*/
nv = xlog_kvmalloc(sizeof(struct xfs_attri_log_nameval) +
name_len + value_len);
- if (!nv)
- return nv;
nv->name.i_addr = nv + 1;
nv->name.i_len = name_len;
--
2.33.0
Powered by blists - more mailing lists