From: Philip Li <philip.li@intel.com>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: <lkp@intel.com>, <boris@bur.io>, <chris.mason@fusionio.com>,
<dsterba@suse.com>, <linux-btrfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <oe-kbuild-all@lists.linux.dev>,
<willy@infradead.org>
Subject: Re: [PATCH] btrfs: remove verity Merkle folio from page cache on error
Date: Mon, 17 Aug 2026 13:23:13 +0800 [thread overview]
Message-ID: <aoKawcCHfWigO8Rz@rli9-mobl> (raw)
In-Reply-To: <20260817023726.1731478-1-chenyichong@uniontech.com>
On Mon, Aug 17, 2026 at 10:37:26AM +0800, Yichong Chen wrote:
> Hi,
>
> Thanks for the report.
>
> This was a problem in v1. The patch called filemap_remove_folio(), which is
> not exported and therefore breaks when btrfs is built as a module.
>
> I avoided filemap_remove_folio() in v2, and the patch has since been reworked
> further. The latest version no longer calls filemap_remove_folio():
Thanks for the info, and sorry for the meaningless report, we will improve
the logic to fix the bot.
>
> [PATCH v4] btrfs: retry verity reads for not-uptodate Merkle folios
> https://lore.kernel.org/all/20260722025435.1493093-1-chenyichong@uniontech.com/
>
> Thanks,
> Yichong
>
prev parent reply other threads:[~2026-08-17 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 5:39 [PATCH] btrfs: remove verity Merkle folio from page cache on error Yichong Chen
2026-07-07 5:35 ` Yichong Chen
2026-07-07 5:55 ` [PATCH v2] btrfs: add verity Merkle folio to page cache after reading it Yichong Chen
2026-07-16 16:23 ` Boris Burkov
2026-07-20 3:12 ` Yichong Chen
2026-08-15 0:46 ` [PATCH] btrfs: remove verity Merkle folio from page cache on error kernel test robot
2026-08-17 2:37 ` Yichong Chen
2026-08-17 5:23 ` Philip Li [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=aoKawcCHfWigO8Rz@rli9-mobl \
--to=philip.li@intel.com \
--cc=boris@bur.io \
--cc=chenyichong@uniontech.com \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=willy@infradead.org \
/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