From: Mikulas Patocka <mpatocka@redhat.com>
To: Dongsheng Yang <dongsheng.yang@linux.dev>
Cc: Li Chen <me@linux.beauty>,
Linux Device Mapper <dm-devel@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zheng Gu <cengku@gmail.com>
Subject: Re: [PATCH v2 0/3] dm-pcache: built-in support and metadata hardening
Date: Tue, 18 Nov 2025 19:05:52 +0100 (CET) [thread overview]
Message-ID: <881e9a2a-0a9e-dda4-1b2f-e208d942898a@redhat.com> (raw)
In-Reply-To: <520bf329-8e3b-4b27-9bd5-82092d501174@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
On Thu, 13 Nov 2025, Dongsheng Yang wrote:
> Hi Mikulas,
>
> Please consider taking these three patches.
>
> Thanx
>
> Dongsheng
OK, thanks. I accepted the patches and I staged them for the kernel 6.18.
Mikulas
> 在 11/11/2025 8:13 PM, Li Chen 写道:
> > From: Li Chen <chenl311@chinatelecom.cn>
> >
> > This three-patch series tidies dm-pcache’s build glue and tightens the
> > metadata scan.
> >
> > Patch 1 allow dm-pcache to be linked into vmlinux and avoids clashing with
> > the sunrpc
> > cache_flush() by using obj-$(CONFIG_DM_PCACHE) and renaming the helper
> > across the tree.
> >
> > Patch 2 drops a redundant recomputation of the metadata slot pointer while
> > walking headers.
> >
> > Patch 3 Ensure dm-pcache initializes cache_info from a zeroed state so
> > metadata CRC
> > failures can’t leak stale flags into the new-cache path.
> >
> > Thanks for your review.
> >
> > Li Chen (3):
> > dm-pcache: allow built-in build and rename flush helper
> > dm-pcache: reuse meta_addr in pcache_meta_find_latest
> > dm-pcache: zero cache_info before default init
> >
> > drivers/md/dm-pcache/Makefile | 2 +-
> > drivers/md/dm-pcache/cache.c | 4 ++--
> > drivers/md/dm-pcache/cache.h | 2 +-
> > drivers/md/dm-pcache/cache_req.c | 6 +++---
> > drivers/md/dm-pcache/pcache_internal.h | 2 +-
> > 5 files changed, 8 insertions(+), 8 deletions(-)
> >
>
prev parent reply other threads:[~2025-11-18 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 12:13 [PATCH v2 0/3] dm-pcache: built-in support and metadata hardening Li Chen
2025-11-11 12:13 ` [PATCH v2 1/3] dm-pcache: allow built-in build and rename flush helper Li Chen
2025-11-13 6:39 ` Dongsheng Yang
2025-11-11 12:13 ` [PATCH v2 2/3] dm-pcache: reuse meta_addr in pcache_meta_find_latest Li Chen
2025-11-13 6:40 ` Dongsheng Yang
2025-11-11 12:13 ` [PATCH v2 3/3] dm-pcache: zero cache_info before default init Li Chen
2025-11-12 8:24 ` Zheng Gu
2025-11-13 6:40 ` Dongsheng Yang
2025-11-13 6:43 ` [PATCH v2 0/3] dm-pcache: built-in support and metadata hardening Dongsheng Yang
2025-11-18 18:05 ` Mikulas Patocka [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=881e9a2a-0a9e-dda4-1b2f-e208d942898a@redhat.com \
--to=mpatocka@redhat.com \
--cc=cengku@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=dongsheng.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=me@linux.beauty \
/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