Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Boris Burkov <boris@bur.io>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [RFC PATCH] btrfs: trigger cow fixup via dirty_folio()
Date: Mon, 27 Jul 2026 15:01:32 +0930	[thread overview]
Message-ID: <eb9c30ad-8c19-4788-83ee-d282ddbdfd97@suse.com> (raw)
In-Reply-To: <20260727035702.GA302657@zen.localdomain>



在 2026/7/27 13:27, Boris Burkov 写道:
[...]
>> Shouldn't we also check if we have cleared the last fixup bit and clear the
>> folio fixup flag?
>> [...]
>>> +void btrfs_folio_cancel_fixup(const struct btrfs_fs_info *fs_info,
>>> +			      struct folio *folio, u64 start, u32 len)
>>
>> Why not let IMPLEMNT_BTRFS_PAGE_OPS() to implement all the fixup helpers?
>>
> 
> I think the level 0 answer is it doesn't apply to metadata and the llm
> also went nuts messing with the macros when it tried to use them.

Right, metadata doesn't need such fixup handling at all, thus we will 
need to split the set/clear into (data|meta)_(set|clear)_func(), which 
is a little overkilled for a hot fix.

Although it would still be good to implement something like 
btrfs_folio_set_fixup() and btrfs_folio_clear_fixup(), so that we do not 
need to expose btrfs_is_subpage() checks.

And we can integrate the fixup cancelling into btrfs_folio_set_dirty() 
helper later, in a dedicated cleanup/refactor series.

Thanks,
Qu

      reply	other threads:[~2026-07-27  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  6:24 [RFC PATCH] btrfs: trigger cow fixup via dirty_folio() Boris Burkov
2026-07-25 10:04 ` Qu Wenruo
2026-07-25 20:12   ` Boris Burkov
2026-07-25 22:19     ` Qu Wenruo
2026-07-27  3:57   ` Boris Burkov
2026-07-27  5:31     ` Qu Wenruo [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=eb9c30ad-8c19-4788-83ee-d282ddbdfd97@suse.com \
    --to=wqu@suse.com \
    --cc=boris@bur.io \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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