All of lore.kernel.org
 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 3/3] dm pcache: fix segment info indexing
Date: Fri, 5 Dec 2025 11:05:24 +0800	[thread overview]
Message-ID: <171cb449-87bf-4e4f-80be-fd16e9f0319b@linux.dev> (raw)
In-Reply-To: <1f27a4db-929a-4271-6628-c2816f3d78fe@redhat.com>


在 12/4/2025 11:59 PM, Mikulas Patocka 写道:
>
> On Thu, 4 Dec 2025, Dongsheng Yang wrote:
>
>> From: Li Chen <chenl311@chinatelecom.cn>
>>
>> Segment info indexing also used sizeof(struct) instead of the
>> 4K metadata stride, so info_index could point between slots and
>> subsequent writes would advance incorrectly. Derive info_index
>> from the pointer returned by the segment meta search using
>> PCACHE_SEG_INFO_SIZE and advance to the next slot for future
>> updates.
>>
>> Signed-off-by: Li Chen <chenl311@chinatelecom.cn>
>> Signed-off-by: Dongsheng Yang <dongsheng.yang@linux.dev>
>> ---
>>   drivers/md/dm-pcache/cache_segment.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/md/dm-pcache/cache_segment.c b/drivers/md/dm-pcache/cache_segment.c
>> index ae57cc261422..9d92e2b067ed 100644
>> --- a/drivers/md/dm-pcache/cache_segment.c
>> +++ b/drivers/md/dm-pcache/cache_segment.c
>> @@ -56,7 +56,10 @@ static int cache_seg_info_load(struct pcache_cache_segment *cache_seg)
>>   		ret = -EIO;
>>   		goto out;
>>   	}
>> -	cache_seg->info_index = cache_seg_info_addr - cache_seg_info_addr_base;
>> +
>> +	cache_seg->info_index =
>> +		((char *)cache_seg_info_addr - (char *)cache_seg_info_addr_base) /
>> +		PCACHE_SEG_INFO_SIZE;
>>   out:
>>   	mutex_unlock(&cache_seg->info_lock);
>>   
> Hi
>
> I already staged the patch below. Which patch is valid? Your new patch or
> the patch that I staged?


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_segment.c
> b/drivers/md/dm-pcache/cache_segment.c
> index f0b58980806e..0b4bb08011ce 100644
> --- a/drivers/md/dm-pcache/cache_segment.c
> +++ b/drivers/md/dm-pcache/cache_segment.c
> @@ -56,7 +56,11 @@ static int cache_seg_info_load(struct
> pcache_cache_segment *cache_seg)
>                  ret = -EIO;
>                  goto out;
>          }
> -       cache_seg->info_index = cache_seg_info_addr - cache_seg_info_addr_base;
> +
> +       cache_seg->info_index =
> +               ((char *)cache_seg_info_addr - (char *)cache_seg_info_addr_base) /
> +               PCACHE_SEG_INFO_SIZE;
> +       cache_seg->info_index = (cache_seg->info_index + 1) % PCACHE_META_INDEX_MAX;
>   out:
>          mutex_unlock(&cache_seg->info_lock);
>
>

  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
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 [this message]
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=171cb449-87bf-4e4f-80be-fd16e9f0319b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.