From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-183.mta0.migadu.com (out-183.mta0.migadu.com [91.218.175.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B42E8320A0B for ; Thu, 13 Nov 2025 06:43:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763016234; cv=none; b=SjKCBQn7VhzsK4qkKYQye+2yv83GRlE+51sJhji3wn55GOMIFsn0pnXy3l3vkMr1fJ3xSGKMlCABc4wMCwaxSRCofIFgUbd8+cab7Js0bDqmlOKrdiS7k6hWihKc90awX7b1Wk1FmOxkQsMtnPPQnWq6du3wKnB/6qLQxqpe2W8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763016234; c=relaxed/simple; bh=tSYubWD2DzdeMFCtkfp6zGvGN6OjzN7OK2x4amL0ixE=; h=Message-ID:Date:MIME-Version:Subject:To:References:Cc:From: In-Reply-To:Content-Type; b=jrFee8bR28JhuwzwmXMJa5o/3AlOYFPU3pWWotgsBtf26xIk4ih/RnzvzESb49WJa2yMztikq0CD1nqokhUAA087AUO94UWMUMsLCpNcOZVOwPEygxg2WzgWsvEzQSHafLmjV0SgGJogg5KfkIyVajECsAqOuBupre2Lyp73iiQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=bFSc3Vf5; arc=none smtp.client-ip=91.218.175.183 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="bFSc3Vf5" Message-ID: <520bf329-8e3b-4b27-9bd5-82092d501174@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1763016230; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HYYGUn2P3Y/iSITP6NTSnslXySDF9DeF8ONeprLe5FE=; b=bFSc3Vf5Tll60JAOuChtaglxPn2qJ35dWkXnjXPWZQ/T+mz0S1IM7ewAEpdH57pM4CqrHO yGvg14mWBc33eXYRy86LeNd7yrkbU1Qmt45eCdky8X8LIcJkboQLbQqRO5H5Y+UqzdTsdv imoxGjMk4szjXhPLL+WIKeYjxB9LD2I= Date: Thu, 13 Nov 2025 14:43:19 +0800 Precedence: bulk X-Mailing-List: dm-devel@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v2 0/3] dm-pcache: built-in support and metadata hardening To: Mikulas Patocka References: <20251111121337.1063443-1-me@linux.beauty> Cc: Li Chen , Linux Device Mapper , Linux Kernel Mailing List , Zheng Gu X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Dongsheng Yang In-Reply-To: <20251111121337.1063443-1-me@linux.beauty> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT Hi Mikulas,     Please consider taking these three patches. Thanx Dongsheng 在 11/11/2025 8:13 PM, Li Chen 写道: > From: Li Chen > > 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(-) >