From: Chao Yu <chao@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2] ext4: fix to report fstrim.minlen back to userspace
Date: Mon, 5 Jun 2023 12:15:14 +0800 [thread overview]
Message-ID: <4f0d6bd4-f393-9879-37c2-2495db4506c9@kernel.org> (raw)
In-Reply-To: <20230421093940.k2crghkblpx2fqlv@quack3>
Ping,
On 2023/4/21 17:39, Jan Kara wrote:
> On Thu 06-04-23 23:04:10, Chao Yu wrote:
>> Quoted from manual of fstrim(8):
>>
>> "-m, --minimum minimum-size
>> ..., if it's smaller than the device's minimum, and report that
>> (fstrim_range.minlen) back to userspace."
>>
>> So this patch tries to report adjusted fstrim_range.minlen back to
>> userspace via FITRIM interface, if the value is smaller than device's
>> minimum discard granularity.
>>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>
> Looks good to me. Feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> Honza
>
>> ---
>> v2:
>> - fix the wrong calculation of range->minlen.
>> fs/ext4/mballoc.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
>> index d8b9d6a83d1e..4af51a16fc64 100644
>> --- a/fs/ext4/mballoc.c
>> +++ b/fs/ext4/mballoc.c
>> @@ -6491,6 +6491,10 @@ int ext4_trim_fs(struct super_block *sb, struct fstrim_range *range)
>> discard_granularity >> sb->s_blocksize_bits);
>> if (minlen > EXT4_CLUSTERS_PER_GROUP(sb))
>> goto out;
>> +
>> + /* Report adjusted minlen back to userspace */
>> + range->minlen = EXT4_C2B(EXT4_SB(sb), minlen) <<
>> + sb->s_blocksize_bits;
>> }
>> if (end >= max_blks - 1) {
>> end = max_blks - 1;
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2023-06-05 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 15:04 [PATCH v2] ext4: fix to report fstrim.minlen back to userspace Chao Yu
2023-04-21 9:39 ` Jan Kara
2023-06-05 4:15 ` Chao Yu [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=4f0d6bd4-f393-9879-37c2-2495db4506c9@kernel.org \
--to=chao@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--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