From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 0/2] btrfs: enhance function extent_range_clear_dirty_for_io()
Date: Tue, 2 Jul 2024 18:43:06 +0200 [thread overview]
Message-ID: <20240702164306.GJ21023@twin.jikos.cz> (raw)
In-Reply-To: <cover.1716427131.git.wqu@suse.com>
On Thu, May 23, 2024 at 10:49:36AM +0930, Qu Wenruo wrote:
> [Changelog]
> v3:
> - Drop the patch to use subpage helper
> For subpage cases, fsstress with compression can lead to hang where
> OE seems hanging and never to be finished.
> So far it looks like some race with i_size change but still not sure
> why the code change is involved.
> Drop the subpage helper change for now.
>
> v2:
> - Split the original patch into 3
>
> - Return the error from filemap_get_folio() to be future-proof
>
> - Enhance the comments for the new ASSERT() on
> extent_range_clear_dirty_for_io() error
> In fact, even if some pages are missing, we do not need to handle the
> error at compress_file_range(), as btrfs_compress_folios() and each
> compression routine would handle the missing folio correctly.
>
> Thus the new ASSERT() is only an early warning for developers.
>
> Qu Wenruo (2):
> btrfs: move extent_range_clear_dirty_for_io() into inode.c
> btrfs: remove the BUG_ON() inside extent_range_clear_dirty_for_io()
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2024-07-02 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 1:19 [PATCH v3 0/2] btrfs: enhance function extent_range_clear_dirty_for_io() Qu Wenruo
2024-05-23 1:19 ` [PATCH v3 1/2] btrfs: move extent_range_clear_dirty_for_io() into inode.c Qu Wenruo
2024-05-23 1:19 ` [PATCH v3 2/2] btrfs: remove the BUG_ON() inside extent_range_clear_dirty_for_io() Qu Wenruo
2024-07-02 16:43 ` David Sterba [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=20240702164306.GJ21023@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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