From: Li Chen <me@linux.beauty>
To: "Dongsheng Yang" <dongsheng.yang@linux.dev>
Cc: "Zheng Gu" <cengku@gmail.com>,
"dm-devel" <dm-devel@lists.linux.dev>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] dm-pcache: avoid leaking invalid metadata in pcache_meta_find_latest()
Date: Tue, 04 Nov 2025 21:36:23 +0800 [thread overview]
Message-ID: <19a4f153cdf.4d1effd9893048.2344913209212358613@linux.beauty> (raw)
In-Reply-To: <1248c78a-c471-496b-b7ac-892ac7335a08@linux.dev>
Hi Dongsheng,
---- On Tue, 04 Nov 2025 14:46:33 +0800 Dongsheng Yang <dongsheng.yang@linux.dev> wrote ---
>
> 在 11/1/2025 9:10 PM, Li Chen 写道:
> > Hi Zheng,
> >
> > ---- On Fri, 31 Oct 2025 10:01:23 +0800 Zheng Gu <cengku@gmail.com> wrote ---
> > >> On Thu, Oct 30, 2025 at 8:36 PM Li Chen <me@linux.beauty> wrote:From: Li Chen <chenl311@chinatelecom.cn>
> > >>
> > >> Before this change pcache_meta_find_latest() was copying each
> > >> slot directly into meta_ret while scanning. If no valid slot
> > >> was found and the function returned NULL, meta_ret still held
> > >> whatever was last copied (possibly CRC-bad). Later users
> > >> (e.g. cache_segs_init) could mistakenly trust that data.
> > >
> > > This functions is * __must_check*, users must check the return value first before touching the meta_ret, so it should not be a problem here.
> >
> > Right now, the callers only check the return value with IS_ERR(). If the
> > function returns NULL instead of an error pointer, a caller like
> > cache_info_init() will assume that no valid cache_info was found because all cache_info are
> > corrupted. Instead, it will try to init a new one, and then return 0 (success),
> > https://github.com/torvalds/linux/blob/master/drivers/md/dm-pcache/cache.c#L61
> >
> > Later, cache_tail_init() will access cache->cache_info.flags. But in this
> > path all cache_info may have already been corrupted, and the CRCs are mismatched
> > (https://github.com/torvalds/linux/blob/ba36dd5ee6fd4643ebbf6ee6eefcecf0b07e35c7/drivers/md/dm-pcache/pcache_internal.h#L97),
> > so flags may contain garbage.
> >
> > This commit fixes this issue by allocating a temp buffer with kvmalloc, so meta_ret would never
> > contain corrupted values.
>
> Hi
>
> Thanx for your fix. So the better change should be reseting
> cache_info in cache_info_init_default() firstly by memset() with 0.
>
> Allocating a temp buffer in pcache_meta_find_latest() is really not a
> good idea.
I considered using memset before sending the patch, but a temporary buffer seems more elegant.
Since the variable is relatively large, I avoided stack allocation. If you prefer memset, should it be implemented
within pcache_meta_find_latest or all its callers?
Regards,
Li
next prev parent reply other threads:[~2025-11-04 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 12:33 [PATCH 0/3] dm-pcache: built-in support and metadata hardening Li Chen
2025-10-30 12:33 ` [PATCH 1/3] dm-pcache: allow built-in build and rename flush helper Li Chen
2025-10-30 12:33 ` [PATCH 2/3] dm-pcache: reuse meta_addr in pcache_meta_find_latest Li Chen
2025-10-30 12:33 ` [PATCH 3/3] dm-pcache: avoid leaking invalid metadata in pcache_meta_find_latest() Li Chen
[not found] ` <CADSj-VoQerDc2UUfBOknRMGetSddMEqRKaC3VDniD+xCq0pH1g@mail.gmail.com>
2025-11-01 13:10 ` Li Chen
2025-11-04 6:46 ` Dongsheng Yang
2025-11-04 13:36 ` Li Chen [this message]
2025-11-05 1:16 ` Dongsheng Yang
2025-11-03 11:38 ` Jonathan Cameron
2025-11-04 12:19 ` Li Chen
2025-11-05 8:46 [PATCH 0/3] dm-pcache: built-in support and metadata hardening Li Chen
2025-11-05 8:46 ` [PATCH 3/3] dm-pcache: avoid leaking invalid metadata in pcache_meta_find_latest() Li Chen
2025-11-10 11:18 ` Dongsheng Yang
2025-11-10 12:32 ` Li Chen
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=19a4f153cdf.4d1effd9893048.2344913209212358613@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
all inboxes | Powered by JetHome®