Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chao Yu <chao@kernel.org>
Subject: [PATCH] ext4: fix wrong calculation of minlen in ext4_trim_fs()
Date: Thu,  6 Apr 2023 23:06:21 +0800	[thread overview]
Message-ID: <20230406150621.3854298-1-chao@kernel.org> (raw)

As Ted pointed out as below:

"
However the minlen variable in ext4_trim_fs is in units of *clusters*.
And so it gets rounded up two places.  The first time is when it is
converted into units of a cluster:

	minlen = EXT4_NUM_B2C(EXT4_SB(sb),
			      range->minlen >> sb->s_blocksize_bits);

Oh, and by the way, that first conversion is not correct as currently
written in ext4_fs_trim().   It should be

	minlen = (range->minlen + EXT4_CLUSTER_SIZE(sb) - 1) >>
		(sb->s_blocksize_bits + EXT4_CLUSTER_BITS(sb));
"

The reason is if range->minlen is smaller than block size of ext4,
original calculation "range->minlen >> sb->s_blocksize_bits" may
return zero, but since EXT4_NUM_B2C() expects a non-zero in-parameter,
so it needs to round up range->minlen to cluster size directly as above.

Link: https://lore.kernel.org/lkml/20230311031843.GF860405@mit.edu/
Suggested-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Chao Yu <chao@kernel.org>
---
 fs/ext4/mballoc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 5b2ae37a8b80..d8b9d6a83d1e 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -6478,8 +6478,8 @@ int ext4_trim_fs(struct super_block *sb, struct fstrim_range *range)
 
 	start = range->start >> sb->s_blocksize_bits;
 	end = start + (range->len >> sb->s_blocksize_bits) - 1;
-	minlen = EXT4_NUM_B2C(EXT4_SB(sb),
-			      range->minlen >> sb->s_blocksize_bits);
+	minlen = (range->minlen + EXT4_CLUSTER_SIZE(sb) - 1) >>
+			(sb->s_blocksize_bits + EXT4_CLUSTER_BITS(sb));
 
 	if (minlen > EXT4_CLUSTERS_PER_GROUP(sb) ||
 	    start >= max_blks ||
-- 
2.25.1


             reply	other threads:[~2023-04-06 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 15:06 Chao Yu [this message]
2023-04-21  9:35 ` [PATCH] ext4: fix wrong calculation of minlen in ext4_trim_fs() Jan Kara
2023-06-05  4:15   ` Chao Yu

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=20230406150621.3854298-1-chao@kernel.org \
    --to=chao@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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