From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: remove COW fixup and checked folio flag
Date: Mon, 13 Apr 2026 19:49:12 +0200 [thread overview]
Message-ID: <20260413174912.GA12792@suse.cz> (raw)
In-Reply-To: <cover.1775621833.git.wqu@suse.com>
On Wed, Apr 08, 2026 at 01:55:30PM +0930, Qu Wenruo wrote:
> For experimental builds we're already rejecting dirty folios which
> don't have ordered flags since v6.15.
>
> Unfortunately we're not yet removing that COW fixup machanism for
> non-experimental builds even at v7.0, as there are still some error
> corner cases that can lead to dirty folios without ordered flags.
>
> After those years of testing, we're sure we won't need COW fixup for
> regular cases. Although I want to remove the COW fixup mechanism after
> all known reproducible cases are fixed, I run out of ideas.
I don't know if I understand this correctly, are there known bugs that
the fixup can catch, but there are not known fixes/root causes?
> Furthermore for the future of huge folios (order 9, 2M page on 4K page
> size systems), we can not afford the extra bitmap for a huge folio.
> In that case, a huge folio will need 64 bytes per bitmap, which is no
> longer a small amount.
>
> I believe it's time to remove the COW fixup mechanism even for
> non-experimental builds, along with the checked folio flags.
Yes please, it has served us well and caused some scars but now it's
dead code.
next prev parent reply other threads:[~2026-04-13 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 4:25 [PATCH 0/2] btrfs: remove COW fixup and checked folio flag Qu Wenruo
2026-04-08 4:25 ` [PATCH 1/2] btrfs: remove the COW fixup mechanism Qu Wenruo
2026-04-13 17:50 ` David Sterba
2026-04-08 4:25 ` [PATCH 2/2] btrfs: remove folio checked subpage bitmap tracking Qu Wenruo
2026-04-13 17:49 ` David Sterba [this message]
2026-04-13 21:46 ` [PATCH 0/2] btrfs: remove COW fixup and checked folio flag 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=20260413174912.GA12792@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.