From: Ramesh Adhikari <adhikari.resume@gmail.com>
To: axboe@kernel.dk, gregkh@linuxfoundation.org
Cc: linux-block@vger.kernel.org, Ramesh Adhikari <adhikari.resume@gmail.com>
Subject: [PATCH] badblocks: fix infinite loop due to incorrect rounding and overflow
Date: Mon, 27 Apr 2026 20:40:48 +0530 [thread overview]
Message-ID: <20260427151048.756072-1-adhikari.resume@gmail.com> (raw)
The roundup() and rounddown() macros return the rounded value but
do not modify the input in place. In _badblocks_set(), _badblocks_clear(),
and badblocks_check(), the return values were being discarded, causing
s and target/next to remain unrounded. This resulted in sectors
being calculated from unrounded values, which could lead to sectors
being way too large (or zero), causing infinite loops in the
re_insert/re_clear/re_check loops.
Additionally, add integer overflow checks (s > ULLONG_MAX - sectors)
before the s + sectors calculation in all three functions to prevent
overflow-related issues. Also add early return when sectors becomes
zero after rounding in badblocks_check().
Root cause: When s and sectors have specific values (e.g., from
syzkaller fuzzing via nvdimm ioctl), the unrounded values cause
sectors to be incorrectly calculated. In _badblocks_clear(), this
could result in needing 2^46 iterations to process 2^55 sectors,
triggering RCU stall warnings and effectively hanging the kernel.
Fix by properly capturing the return values from roundup() and
rounddown(), adding overflow checks before sector arithmetic, and
handling the zero-sectors case in badblocks_check().
Signed-off-by: Ramesh Adhikari <adhikari.resume@gmail.com>
---
block/badblocks.c | 43 ++++++++++++++++++++++++++++++++++---------
1 file changed, 34 insertions(+), 9 deletions(-)
diff --git a/block/badblocks.c b/block/badblocks.c
index ece64e76fe8..a5ffae65a05 100644
--- a/block/badblocks.c
+++ b/block/badblocks.c
@@ -855,13 +855,21 @@ static bool _badblocks_set(struct badblocks *bb, sector_t s, sector_t sectors,
if (bb->shift) {
/* round the start down, and the end up */
+ if (s > ULLONG_MAX - sectors)
+ return false;
sector_t next = s + sectors;
- rounddown(s, 1 << bb->shift);
- roundup(next, 1 << bb->shift);
- sectors = next - s;
+ s = rounddown(s, 1 << bb->shift);
+ next = roundup(next, 1 << bb->shift);
+ if (next < s)
+ sectors = 0;
+ else
+ sectors = next - s;
}
+ if (sectors == 0)
+ return false;
+
write_seqlock_irqsave(&bb->lock, flags);
bad.ack = acknowledged;
@@ -1070,12 +1078,20 @@ static bool _badblocks_clear(struct badblocks *bb, sector_t s, sector_t sectors)
* However it is better the think a block is bad when it
* isn't than to think a block is not bad when it is.
*/
+ if (s > ULLONG_MAX - sectors)
+ return false;
target = s + sectors;
- roundup(s, 1 << bb->shift);
- rounddown(target, 1 << bb->shift);
- sectors = target - s;
+ s = roundup(s, 1 << bb->shift);
+ target = rounddown(target, 1 << bb->shift);
+ if (target < s)
+ sectors = 0;
+ else
+ sectors = target - s;
}
+ if (sectors == 0)
+ return false;
+
write_seqlock_irq(&bb->lock);
bad.ack = true;
@@ -1305,11 +1321,20 @@ int badblocks_check(struct badblocks *bb, sector_t s, sector_t sectors,
if (bb->shift > 0) {
/* round the start down, and the end up */
+ if (s > ULLONG_MAX - sectors) {
+ return -EINVAL;
+ }
sector_t target = s + sectors;
- rounddown(s, 1 << bb->shift);
- roundup(target, 1 << bb->shift);
- sectors = target - s;
+ s = rounddown(s, 1 << bb->shift);
+ target = roundup(target, 1 << bb->shift);
+ if (target < s)
+ sectors = 0;
+ else
+ sectors = target - s;
+
+ if (sectors == 0)
+ return 0;
}
retry:
--
2.43.0
next reply other threads:[~2026-04-27 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 15:10 Ramesh Adhikari [this message]
2026-04-27 15:12 ` [PATCH] badblocks: fix infinite loop due to incorrect rounding and overflow Greg KH
2026-04-29 23:06 ` kernel test robot
2026-04-30 5:09 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260427151048.756072-1-adhikari.resume@gmail.com \
--to=adhikari.resume@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox