mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kaitao Cheng <kaitao.cheng@linux.dev>
To: Nhat Pham <nphamcs@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Yosry Ahmed <yosry@kernel.org>,
	Chengming Zhou <chengming.zhou@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	Muchun Song <muchun.song@linux.dev>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: Re: [PATCH] mm/zswap: fix double decrement of the LRU node count on writeback
Date: Thu, 29 Oct 2026 12:15:23 +0800	[thread overview]
Message-ID: <3410e049-2e61-4ab1-b776-e77f3b97517f@linux.dev> (raw)
In-Reply-To: <CAKEwX=NfFNbBwhvNpYz8iWgimFuOow8J8x1SzV_6GcC_bb=Etg@mail.gmail.com>



在 2026/10/29 02:47, Nhat Pham 写道:
> On Wed, Oct 28, 2026 at 4:36 AM Kaitao Cheng <kaitao.cheng@linux.dev> wrote:
>>
>> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>>
>> Successful writeback calls zswap_entry_free(), which removes the entry
>> from the LRU and decrements both the sublist and node item counts.
>> shrink_memcg_cb() then returns LRU_REMOVED_RETRY, causing the LRU walker
>> to decrement the node count again.
>>
>> The affected call path before this change is:
>>
>>   __list_lru_walk_one()
>>     shrink_memcg_cb()
>>       zswap_writeback_entry()
>>         zswap_entry_free()
>>           zswap_lru_del()
>>             list_lru_del()
>>               __list_lru_del()
>>                 atomic_long_dec()  /* first node count decrement */
>>       return LRU_REMOVED_RETRY
>>     atomic_long_dec()              /* second node count decrement */
>>
>> Add zswap_lru_del_nocnt() to remove the entry and update only the sublist
>> count, leaving node accounting to the walker. Split data cleanup into
>> __zswap_entry_free() so writeback can free the entry without performing
>> another LRU deletion. Other free paths retain their existing accounting.
> 
> What is the visible effect? Is there any effect, be it in reclaim
> dynamics or userspace counters? Can you add it to the changelog?
> 
> I'm not against fixing it, but need to gauge the effect for
> prioritization, whether to cc stable etc. etc.
> 

This is only an accounting issue; I could not find any code in zswap that
reads lru->node[nid].nr_items.

>>
>> Fixes: 5878303c5353 ("mm/zswap: fix race between lru writeback and swapoff")
>> Link: https://sashiko.dev/#/bug/linux-68d2ca49-23be-4504-9a75-b8526ec92388
>> Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>

-- 
Thanks
Kaitao Cheng


  reply	other threads:[~2026-10-29  4:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 11:36 Kaitao Cheng
2026-10-28 18:47 ` Nhat Pham
2026-10-29  4:15   ` Kaitao Cheng [this message]
2026-10-29 17:11     ` Nhat Pham
2026-10-28 19:22 ` Yosry Ahmed
2026-10-28 21:10   ` Johannes Weiner
2026-10-28 21:17     ` Yosry Ahmed
2026-10-29  4:23     ` Kaitao Cheng
2026-10-29 15:10       ` Yosry Ahmed

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=3410e049-2e61-4ab1-b776-e77f3b97517f@linux.dev \
    --to=kaitao.cheng@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=chengkaitao@kylinos.cn \
    --cc=chengming.zhou@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=nphamcs@gmail.com \
    --cc=yosry@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®