From: sashiko-bot@kernel.org
To: "Kaixuan Li" <kaixuanli0131@gmail.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: stop verify_reserved_gdb() one entry short of the block
Date: Sat, 19 Sep 2026 11:46:37 +0000 [thread overview]
Message-ID: <20260919114638.1B2AC1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919113940.1823559-1-kaixuanli0131@gmail.com>
> verify_reserved_gdb() walks the backup group list, reading one __le32 from
> the reserved GDT block per iteration, and bounds the walk after the read:
>
> if (le32_to_cpu(*p++) !=
> grp * EXT4_BLOCKS_PER_GROUP(sb) + blk){
> ...
> return -EINVAL;
> }
> if (++gdbackups > EXT4_ADDR_PER_BLOCK(sb))
> return -EFBIG;
>
> The block holds exactly EXT4_ADDR_PER_BLOCK(sb) entries, so when gdbackups
> reaches that value the test is false, the loop runs once more, and *p++
> reads one entry past the block before -EFBIG is returned. The same value is
> also the largest gdbackups the function can return, and
> [ ... ]
> them, 256 at a 1K block size and 1024 at 4K, cannot occur within a 32-bit
> group number. The entry the old bound went on to read was therefore never a
> real backup.
>
> Signed-off-by: Kaixuan Li <kaixuanli0131@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919113940.1823559-1-kaixuanli0131@gmail.com?part=1
prev parent reply other threads:[~2026-09-19 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 11:39 [PATCH] ext4: stop verify_reserved_gdb() one entry short of the block Kaixuan Li
2026-09-19 11:46 ` sashiko-bot [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=20260919114638.1B2AC1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kaixuanli0131@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.