From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] btrfs: btrfs: fix possible race between error handling and writeback
Date: Thu, 21 Aug 2025 15:52:34 +0200 [thread overview]
Message-ID: <20250821135234.GT22430@suse.cz> (raw)
In-Reply-To: <afd0e356-973c-4007-9603-88d690bb23aa@gmx.com>
On Tue, Aug 19, 2025 at 07:17:28AM +0930, Qu Wenruo wrote:
> 在 2025/8/19 01:18, David Sterba 写道:
> > On Mon, Jul 28, 2025 at 05:57:53PM +0930, Qu Wenruo wrote:
> >> Qu Wenruo (4):
> >> btrfs: rework the error handling of run_delalloc_nocow()
> >> btrfs: enhance error messages for delalloc range failure
> >> btrfs: make nocow_one_range() to do cleanup on error
> >> btrfs: keep folios locked inside run_delalloc_nocow()
> >
> > The patches have been in linux-next for some time, feel free to add them
> > to for-next proper so they can be merged. Related to that, you can
> > remove the cow fixup code in this development cycle if you want.
> >
>
> Unfortunately even with this series applies, I'm still hitting COW fixup
> warning at a very low chance for g/475.
>
> So I'm afraid we're not yet done about all the possible error paths,
> thus no removal of cow fixup yet.
I see. Alternatively the cow fixup can be turned to proper debugging
mechanism so you can still use it to catch bugs but it does not need to
have the whole fixup mechanism. If we can get rid of the fixup worker
kthread it would still be a good incremental step as it's just idling
and consuming rerources.
prev parent reply other threads:[~2025-08-21 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 8:27 [PATCH v2 0/4] btrfs: btrfs: fix possible race between error handling and writeback Qu Wenruo
2025-07-28 8:27 ` [PATCH v2 1/4] btrfs: rework the error handling of run_delalloc_nocow() Qu Wenruo
2025-07-28 8:27 ` [PATCH v2 2/4] btrfs: enhance error messages for delalloc range failure Qu Wenruo
2025-07-28 8:27 ` [PATCH v2 3/4] btrfs: make nocow_one_range() to do cleanup on error Qu Wenruo
2025-07-28 8:27 ` [PATCH v2 4/4] btrfs: keep folios locked inside run_delalloc_nocow() Qu Wenruo
2025-08-04 22:36 ` Wang Yugui
2025-08-04 22:53 ` Qu Wenruo
2025-08-18 15:48 ` [PATCH v2 0/4] btrfs: btrfs: fix possible race between error handling and writeback David Sterba
2025-08-18 21:47 ` Qu Wenruo
2025-08-21 13:52 ` 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=20250821135234.GT22430@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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