From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/2] btrfs: remove the COW fixup mechanism
Date: Tue, 14 Apr 2026 04:14:13 +0200 [thread overview]
Message-ID: <20260414021413.GL12792@twin.jikos.cz> (raw)
In-Reply-To: <5f9c367ba3f2c32972d0bc2844858bfb1fd47061.1776129347.git.wqu@suse.com>
On Tue, Apr 14, 2026 at 10:46:41AM +0930, Qu Wenruo wrote:
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -1739,12 +1739,6 @@ static noinline_for_stack int extent_writepage_io(struct btrfs_inode *inode,
> start, len, folio_start, folio_size(folio));
>
> ret = btrfs_writepage_cow_fixup(folio);
The btrfs_writepage_cow_fixup() is left to do the check but now the name
does not match what it's doing, it basically verifies the ordered bit is
set or return EUCLEAN.
Either here or in a separate patch please rename it, to something like
"verify ordered" or something describing what we expect here so we can
forget about what 'fixup' meant.
> - if (ret == -EAGAIN) {
> - /* Fixup worker will requeue */
> - folio_redirty_for_writepage(bio_ctrl->wbc, folio);
> - folio_unlock(folio);
> - return 1;
> - }
> if (ret < 0) {
> btrfs_folio_clear_dirty(fs_info, folio, start, len);
> btrfs_folio_set_writeback(fs_info, folio, start, len);
next prev parent reply other threads:[~2026-04-14 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 1:16 [PATCH v2 0/2] btrfs: remove COW fixup and checked folio flag Qu Wenruo
2026-04-14 1:16 ` [PATCH v2 1/2] btrfs: remove the COW fixup mechanism Qu Wenruo
2026-04-14 2:14 ` David Sterba [this message]
2026-04-14 1:16 ` [PATCH v2 2/2] btrfs: remove folio checked subpage bitmap tracking Qu Wenruo
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=20260414021413.GL12792@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