From: Ramesh Adhikari <adhikari.resume@gmail.com>
To: colyli@fygo.io, axboe@kernel.dk
Cc: gregkh@linuxfoundation.org, linux-block@vger.kernel.org,
stable@vger.kernel.org,
Ramesh Adhikari <adhikari.resume@gmail.com>
Subject: [PATCH v6 0/2] badblocks: fix infinite loop and validate sector range/shift
Date: Thu, 9 Jul 2026 18:49:02 +0530 [thread overview]
Message-ID: <20260709131904.596684-1-adhikari.resume@gmail.com> (raw)
In-Reply-To: <ak9CC591ivuQ4BP1@studio.local>
This replaces the single-patch v5 with a two-patch series, per Coly's
review.
v1-v4 chased symptoms of the same underlying bug (an RCU stall found
by syzkaller through the nvdimm ioctl path, in _badblocks_check() /
badblocks_check() looping with a non-advancing range) before landing
on the root cause in v4: rounddown()/roundup() don't modify their
argument in place, so 's'/'next'/'target' were never actually
rounded.
v5 folded the round_down()/round_up() fix together with overflow and
zero-length guards into one patch. Coly's review on v5 pointed out
that:
- the overflow check that was there wasn't sufficient on its own
(only one of several range-validity conditions), and
- the round fix and the validation should be separate patches,
since they're independently useful and one is safe to backport
on its own.
This series:
1/2 is exactly the round_down()/round_up() fix, nothing else. This
is what actually stops the infinite loop and also fixes the
32-bit build breakage kernel test robot reported on v1
(rounddown()/roundup() do 64-bit division/modulo on sector_t,
requiring libgcc helpers not linked into the kernel).
2/2 adds the range/shift validation Coly asked for: s+sectors
overflow, bb->shift too large to shift a sector_t by (bb->shift
is populated in drivers/md/md.c straight from an unvalidated
on-disk superblock byte), and detecting when round_up()/
round_down() themselves wrap near ULLONG_MAX.
Both are tagged Fixes: aa511ff8218b ("badblocks: switch to the
improved badblock handling code") and Cc: stable, since that's the
commit that introduced this code path.
Ramesh Adhikari (2):
badblocks: fix in-place round_up/round_down usage bug
badblocks: validate sector range and shift before rounding
block/badblocks.c | 52 ++++++++++++++++++++++++++++++++++++++++-------
1 file changed, 45 insertions(+), 7 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-07-09 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 15:10 [PATCH] badblocks: fix infinite loop due to incorrect rounding and overflow Ramesh Adhikari
2026-04-27 15:12 ` Greg KH
2026-04-29 23:06 ` kernel test robot
2026-04-30 5:09 ` kernel test robot
2026-07-04 17:13 ` [PATCH v5] " Ramesh Adhikari
2026-07-09 10:25 ` Coly Li
2026-07-09 13:19 ` Ramesh Adhikari [this message]
2026-07-09 13:19 ` [PATCH v6 1/2] badblocks: fix in-place round_up/round_down usage bug Ramesh Adhikari
2026-07-09 15:16 ` Coly Li
2026-07-09 13:19 ` [PATCH v6 2/2] badblocks: validate sector range and shift before rounding Ramesh Adhikari
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=20260709131904.596684-1-adhikari.resume@gmail.com \
--to=adhikari.resume@gmail.com \
--cc=axboe@kernel.dk \
--cc=colyli@fygo.io \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=stable@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