Linux block layer
 help / color / mirror / Atom feed
From: "yu kuai" <yukuai@fygo.io>
To: <colyli@fygo.io>, "yu kuai" <yukuai@fygo.io>
Cc: <linux-raid@vger.kernel.org>, <linux-block@vger.kernel.org>,
	 <stable@vger.kernel.org>,
	"Ramesh Adhikari" <adhikari.resume@gmail.com>
Subject: Re: [PATCH] md: do overflow check for sb->bblog_shift in super_1_load()
Date: Fri, 31 Jul 2026 16:00:02 +0800	[thread overview]
Message-ID: <e8e9bb6b-434f-46cd-a30f-2abc7873f3f8@fygo.io> (raw)
In-Reply-To: <20260720111400.2120834-1-colyli@fygo.io>

在 2026/7/20 19:14, colyli@fygo.io 写道:

> From: Coly Li<colyli@fygo.io>
>
> In super_1_load(), sb->bblog_shift is an __u8 type value loaded from on-
> disk superblock. It is used for badblocks API badblocks_set() by the
> following sequence,
>
>   1930   rdev->badblocks.shift = sb->bblog_shift;
>   1931   for (i = 0 ; i < (sectors << (9-3)) ; i++, bbp++) {
>   1932           u64 bb = le64_to_cpu(*bbp);
>   1933           int count = bb & (0x3ff);
>   1934           u64 sector = bb >> 10;
>   1935           sector <<= sb->bblog_shift;
>   1936           count <<= sb->bblog_shift;
>   1937           if (bb + 1 == 0)
>   1938                   break;
>   1939           if (!badblocks_set(&rdev->badblocks, sector, count, 1))
>   1940                   return -EINVAL;
>   1941   }
>
> bb->bblog_shit is in range of 0-255, variable sector is 64bit width, for
> an invalid bb->bblog_shit, it is possible to make sector be overflowed
> by the following calculation,
>   1935           sector <<= sb->bblog_shift;
> Then in turn when call badblocks_set() at line 1939 with the invalid
> rdev->badblocks.shift set at line 1930, may result an overflow inside
> _badblocks_clear() in block/badblocks.c.
>
> Although there are many places to call badblocks APIs, the non-zero
> shift value is only used in super_1_load(), other places always use 0 as
> the shift value. Therefore it is unnecessary to do a general shift value
> overflow check inside badblock API, and just check here as the caller.
>
> This may avoid unnecessary check, make the badblocks API code more simple
> and elegant.
>
> Fixes: 2699b67223aca ("md: load/store badblock list from v1.x metadata")
> Fixes: 1726c77467833 ("badblocks: improve badblocks_set() for multiple ranges handling")
> Cc:stable@vger.kernel.org
> Cc: Ramesh Adhikari<adhikari.resume@gmail.com>
> Signed-off-by: Coly Li<colyli@fygo.io>
> ---
>   drivers/md/md.c | 7 +++++++
>   1 file changed, 7 insertions(+)
Applied to md-7.3

-- 
Thanks,
Kuai

      parent reply	other threads:[~2026-07-31  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 11:14 [PATCH] md: do overflow check for sb->bblog_shift in super_1_load() colyli
2026-07-22  2:29 ` yu kuai
2026-07-31  8:00 ` yu kuai [this message]

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=e8e9bb6b-434f-46cd-a30f-2abc7873f3f8@fygo.io \
    --to=yukuai@fygo.io \
    --cc=adhikari.resume@gmail.com \
    --cc=colyli@fygo.io \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@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