From: Li Chen <me@linux.beauty>
To: dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
Dongsheng Yang <dongsheng.yang@linux.dev>,
Zheng Gu <cengku@gmail.com>
Subject: [PATCH v2 0/3] dm-pcache: built-in support and metadata hardening
Date: Tue, 11 Nov 2025 20:13:33 +0800 [thread overview]
Message-ID: <20251111121337.1063443-1-me@linux.beauty> (raw)
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(-)
--
2.51.0
next reply other threads:[~2025-11-11 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 12:13 Li Chen [this message]
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
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=20251111121337.1063443-1-me@linux.beauty \
--to=me@linux.beauty \
--cc=cengku@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=dongsheng.yang@linux.dev \
--cc=linux-kernel@vger.kernel.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