[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211208075157.404535-1-luo.penghao@zte.com.cn>
Date: Wed, 8 Dec 2021 07:51:57 +0000
From: cgel.zte@...il.com
To: Theodore Ts'o <tytso@....edu>
Cc: Andreas Dilger <adilger.kernel@...ger.ca>,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
luo penghao <luo.penghao@....com.cn>,
Zeal Robot <zealci@....com.cn>
Subject: [PATCH linux-next] ext4: Remove redundant o_start statements
From: luo penghao <luo.penghao@....com.cn>
The if will goto out of the loop, and until the end of the
function execution, o_start will not be used again.
The clang_analyzer complains as follows:
fs/ext4/move_extent.c:635:5 warning:
Value stored to 'o_start' is never read
Reported-by: Zeal Robot <zealci@....com.cn>
Signed-off-by: luo penghao <luo.penghao@....com.cn>
---
fs/ext4/move_extent.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ext4/move_extent.c b/fs/ext4/move_extent.c
index 64a5797..95aa212 100644
--- a/fs/ext4/move_extent.c
+++ b/fs/ext4/move_extent.c
@@ -632,7 +632,6 @@ ext4_move_extents(struct file *o_filp, struct file *d_filp, __u64 orig_blk,
/* Check hole before the start pos */
if (cur_blk + cur_len - 1 < o_start) {
if (next_blk == EXT_MAX_BLOCKS) {
- o_start = o_end;
ret = -ENODATA;
goto out;
}
--
2.15.2
Powered by blists - more mailing lists