[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20230221094244.3631986-1-zhongjinghua@huaweicloud.com>
Date: Tue, 21 Feb 2023 17:42:44 +0800
From: Zhong Jinghua <zhongjinghua@...weicloud.com>
To: axboe@...nel.dk, code@...dh.me, willy@...radead.org
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
zhongjinghua@...wei.com, yi.zhang@...wei.com, yukuai3@...wei.com,
houtao1@...wei.com
Subject: [PATCH-next v3] loop: loop_set_status_from_info() check before assignment
From: Zhong Jinghua <zhongjinghua@...wei.com>
In loop_set_status_from_info(), lo->lo_offset and lo->lo_sizelimit should
be checked before reassignment, because if an overflow error occurs, the
original correct value will be changed to the wrong value, and it will not
be changed back.
Modifying to the wrong value logic is always not quiet right, we hope to
optimize this.
loop_handle_cmd
do_req_filebacked
loff_t pos = ((loff_t) blk_rq_pos(rq) << 9) + lo->lo_offset;
lo_rw_aio
cmd->iocb.ki_pos = pos
Fixes: c490a0b5a4f3 ("loop: Check for overflow while configuring loop")
Signed-off-by: Zhong Jinghua <zhongjinghua@...wei.com>
---
v2: Modify note: overflowing -> overflow
v3: Modify commit message
drivers/block/loop.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 1518a6423279..1b35cbd029c7 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -977,13 +977,13 @@ loop_set_status_from_info(struct loop_device *lo,
return -EINVAL;
}
+ /* Avoid assigning overflow values */
+ if (info->lo_offset > LLONG_MAX || info->lo_sizelimit > LLONG_MAX)
+ return -EOVERFLOW;
+
lo->lo_offset = info->lo_offset;
lo->lo_sizelimit = info->lo_sizelimit;
- /* loff_t vars have been assigned __u64 */
- if (lo->lo_offset < 0 || lo->lo_sizelimit < 0)
- return -EOVERFLOW;
-
memcpy(lo->lo_file_name, info->lo_file_name, LO_NAME_SIZE);
lo->lo_file_name[LO_NAME_SIZE-1] = 0;
lo->lo_flags = info->lo_flags;
--
2.31.1
Powered by blists - more mailing lists