From: Qu Wenruo <wqu@suse.com>
To: Luca Stefani <luca.stefani.ge1@gmail.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: Don't block system suspend during fstrim
Date: Mon, 2 Sep 2024 19:10:57 +0930 [thread overview]
Message-ID: <2e72f744-7262-4d22-a3a1-44a323036ec9@suse.com> (raw)
In-Reply-To: <072aba7d-6571-4b22-875d-3409c0eefe40@gmail.com>
在 2024/9/2 19:01, Luca Stefani 写道:
[...]
>>>
>>> Oh, then it's fine.
>>>
>>> Except the return code, everything looks fine to me now.
>>
>> Forgot to mention that, even for error case, we should copy the
>> fstrim_range structure to the ioctl parameter to indicate any progress
>> we made.
> This seems to be already the case.
> range->len = trimmed; is always executed regardless of previous failures
> and there doesn't seem to be any early return.
What I mean is inside btrfs_ioctl_fitrim(), at the end if
btrfs_trim_fs() returned error (including interrupted), copy_to_user()
will not be call, that's the problem needs to be solved, as long as we
return error for interrupted cases.
Thanks,
Qu
>
> Will try adding back the errno and try the repro.
>
> Thanks.
>>
>> Thanks,
>> Qu
>>>
>>> Just please update the commit message to explicitly mention that, we
>>> have a free extent discarding phase, which can trim a lot of unallocated
>>> space, and there is no limits on the trim size (unlike the block group
>>> part).
>>>
>>> Thanks,
>>> Qu
>>>>
>>>> Thanks,
>>>> Qu
>>>>
>>>> >> }
>>>> >> mutex_unlock(&fs_devices->device_list_mutex);
>>>> >
>>>>
>>>
>
next prev parent reply other threads:[~2024-09-02 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 16:48 Luca Stefani
2024-09-02 8:32 ` Luca Stefani
2024-09-02 8:49 ` Qu Wenruo
[not found] ` <CAO0HQ0X3zk6aau50Ew2nmNP-pwNEkmgAoC2Ewmi30sGi7uQwDA@mail.gmail.com>
2024-09-02 9:12 ` Qu Wenruo
2024-09-02 9:17 ` Qu Wenruo
2024-09-02 9:31 ` Luca Stefani
2024-09-02 9:40 ` Qu Wenruo [this message]
2024-09-02 11:01 ` Qu Wenruo
2024-09-02 11:10 ` Luca Stefani
2024-09-02 9:14 ` Luca Stefani
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=2e72f744-7262-4d22-a3a1-44a323036ec9@suse.com \
--to=wqu@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.com \
--cc=quwenruo.btrfs@gmx.com \
/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
all inboxes | Powered by JetHome®