Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Yichong Chen <chenyichong@uniontech.com>
To: sashiko-bot@kernel.org
Cc: chenyichong@uniontech.com, linux-ext4@vger.kernel.org,
	sashiko-reviews@lists.linux.dev, tytso@mit.edu
Subject: Re: [PATCH] ext4: fix the logical block counter overflow in indirect migration
Date: Mon, 14 Sep 2026 15:38:22 +0800	[thread overview]
Message-ID: <20260914073822.3440595-1-chenyichong@uniontech.com> (raw)
In-Reply-To: <20260914071853.ED58F1F000FF@smtp.kernel.org>

Hi,

Thanks for the review.

The EXT_MAX_BLOCKS point is valid.  An extent may not cover that block,
because ext4_valid_extent() rejects a wrapping ee_block + ee_len, so
ext4_iget() would drop the migrated inode as corrupt.  The bound has to be
>= EXT_MAX_BLOCKS, not > (ext4_lblk_t)-1.  I will send a v2 with that fixed.

Thanks,
Yichong

  reply	other threads:[~2026-09-14  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  6:55 [PATCH] ext4: fix the logical block counter overflow in indirect migration Yichong Chen
2026-09-14  7:18 ` sashiko-bot
2026-09-14  7:38   ` Yichong Chen [this message]
2026-09-14  9:57 ` Jan Kara

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=20260914073822.3440595-1-chenyichong@uniontech.com \
    --to=chenyichong@uniontech.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sashiko-bot@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox