public inbox for dm-devel@redhat.com
 help / color / mirror / Atom feed
From: Dongsheng Yang <dongsheng.yang@linux.dev>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: cengku@gmail.com, dm-devel@lists.linux.dev, chenl311@chinatelecom.cn
Subject: Re: [PATCH 2/3] dm pcache: fix cache info indexing
Date: Fri, 5 Dec 2025 11:05:05 +0800	[thread overview]
Message-ID: <61a94278-617b-4f93-b35e-83b44833d425@linux.dev> (raw)
In-Reply-To: <e40cf2ec-d087-65f9-45a0-a47119c89ced@redhat.com>


在 12/5/2025 12:01 AM, Mikulas Patocka 写道:
>
> On Thu, 4 Dec 2025, Dongsheng Yang wrote:
>
>> From: Li Chen <chenl311@chinatelecom.cn>
>>
>> The on-media cache_info index used sizeof(struct) instead of the
>> 4K metadata stride, so gc_percent updates from dmsetup message
>> were written between slots and lost after reboot. Use
>> PCACHE_CACHE_INFO_SIZE in get_cache_info_addr() and align
>> info_index with the slot returned by pcache_meta_find_latest().
>>
>> Signed-off-by: Li Chen <chenl311@chinatelecom.cn>
>> Signed-off-by: Dongsheng Yang <dongsheng.yang@linux.dev>
>> ---
>>   drivers/md/dm-pcache/cache.c | 8 ++++++--
>>   1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/md/dm-pcache/cache.c b/drivers/md/dm-pcache/cache.c
>> index 9289c016b7c9..bcc4e509aa69 100644
>> --- a/drivers/md/dm-pcache/cache.c
>> +++ b/drivers/md/dm-pcache/cache.c
>> @@ -8,9 +8,11 @@
>>   
>>   struct kmem_cache *key_cache;
>>   
>> -static inline struct pcache_cache_info *get_cache_info_addr(struct pcache_cache *cache)
>> +static inline struct pcache_cache_info *
>> +get_cache_info_addr(struct pcache_cache *cache)
>>   {
>> -	return cache->cache_info_addr + cache->info_index;
>> +	return (struct pcache_cache_info *)((char *)cache->cache_info_addr +
>> +						(size_t)cache->info_index * PCACHE_CACHE_INFO_SIZE);
>>   }
>>   
>>   static void cache_info_write(struct pcache_cache *cache)
>> @@ -49,6 +51,8 @@ static int cache_info_init(struct pcache_cache *cache, struct pcache_cache_optio
>>   			return -EINVAL;
>>   		}
>>   
>> +		cache->info_index = ((char *)cache_info_addr - (char *)cache->cache_info_addr) / PCACHE_CACHE_INFO_SIZE;
>> +
>>   		return 0;
>>   	}
>>   
>> -- 
>> 2.43.0
> I already staged the patch below? Should I revert it and stage your new
> patch?


Yes, please revert it, I will send a v2 patchset, please pick the v2 patch.


Thanx

>
> Mikulas
>
>
> diff --git a/drivers/md/dm-pcache/cache.c b/drivers/md/dm-pcache/cache.c
> index d8e92367d947..9554d1158450 100644
> --- a/drivers/md/dm-pcache/cache.c
> +++ b/drivers/md/dm-pcache/cache.c
> @@ -8,9 +8,11 @@
>
>   struct kmem_cache *key_cache;
>
> -static inline struct pcache_cache_info *get_cache_info_addr(struct pcache_cache *cache)
> +static inline struct pcache_cache_info *
> +get_cache_info_addr(struct pcache_cache *cache)
>   {
> -       return cache->cache_info_addr + cache->info_index;
> +       return (struct pcache_cache_info *)((char *)cache->cache_info_addr
> +
> +                                               (size_t)cache->info_index * PCACHE_CACHE_INFO_SIZE);
>   }
>
>   static void cache_info_write(struct pcache_cache *cache)
> @@ -40,7 +42,12 @@ static int cache_info_init(struct pcache_cache *cache,
> struct pcache_cache_optio
>          if (IS_ERR(cache_info_addr))
>                  return PTR_ERR(cache_info_addr);
>
> -       if (cache_info_addr) {
> +    if (cache_info_addr) {
> +               int index = ((char *)cache_info_addr - (char *)cache->cache_info_addr) /
> +                               PCACHE_CACHE_INFO_SIZE;
> +
> +               cache->info_index = (index + 1) % PCACHE_META_INDEX_MAX;
> +
>                  if (opts->data_crc !=
>                                  (cache->cache_info.flags & PCACHE_CACHE_FLAGS_DATA_CRC)) {
>                          pcache_dev_err(pcache, "invalid option for data_crc: %s, expected: %s",
>

  reply	other threads:[~2025-12-05  3:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  2:53 [PATCH 1/3] dm-pcache: advance slot index before writing slot Dongsheng Yang
2025-12-04  2:53 ` [PATCH 2/3] dm pcache: fix cache info indexing Dongsheng Yang
2025-12-04  3:09   ` Zheng Gu
2025-12-04 16:01   ` Mikulas Patocka
2025-12-05  3:05     ` Dongsheng Yang [this message]
2025-12-04  2:53 ` [PATCH 3/3] dm pcache: fix segment " Dongsheng Yang
2025-12-04  3:10   ` Zheng Gu
2025-12-04 15:59   ` Mikulas Patocka
2025-12-05  3:05     ` Dongsheng Yang
2025-12-04  3:08 ` [PATCH 1/3] dm-pcache: advance slot index before writing slot Zheng Gu
2025-12-04 16:13 ` Mikulas Patocka
2025-12-05  3:01   ` Dongsheng Yang
2025-12-06 11:36     ` 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=61a94278-617b-4f93-b35e-83b44833d425@linux.dev \
    --to=dongsheng.yang@linux.dev \
    --cc=cengku@gmail.com \
    --cc=chenl311@chinatelecom.cn \
    --cc=dm-devel@lists.linux.dev \
    --cc=mpatocka@redhat.com \
    /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