From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Longlong Xia <xialonglong2025@163.com>, akpm@linux-foundation.org
Cc: xu.xin16@zte.com.cn, chengming.zhou@linux.dev,
hugh.dickins@tiscali.co.uk, ieidus@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Longlong Xia <xialonglong@kylinos.cn>
Subject: Re: [PATCH 1/1] mm/ksm: avoid missing ksmd wakeups in ksm_enter
Date: Wed, 5 Aug 2026 14:26:22 +0200 [thread overview]
Message-ID: <6bb83027-07fb-4152-8edd-f349e6fbcc42@kernel.org> (raw)
In-Reply-To: <20260803152115.3479919-1-xialonglong2025@163.com>
On 8/3/26 17:21, Longlong Xia wrote:
> From: Longlong Xia <xialonglong@kylinos.cn>
>
> __ksm_enter() decides whether ksmd needs a wakeup by checking if the
> mm slot list is empty before inserting the new slot.
>
> The empty check is currently outside ksm_mmlist_lock. Another CPU can
> remove the last slot and let ksmd go back to sleep after the unlocked
> check, while this CPU inserts a new slot and skips the wakeup based on
> the stale result.
>
> Take ksm_mmlist_lock before checking the list so the empty-to-nonempty
> transition and the insertion are observed as one critical section.
>
> Fixes: 6e15838425ac ("ksm: keep quiet while list empty")
> Signed-off-by: Longlong Xia <xialonglong@kylinos.cn>
> ---
> mm/ksm.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/mm/ksm.c b/mm/ksm.c
> index 7d5b76478f0b..3f2f4707ca9e 100644
> --- a/mm/ksm.c
> +++ b/mm/ksm.c
> @@ -3019,7 +3019,7 @@ int __ksm_enter(struct mm_struct *mm)
> {
> struct ksm_mm_slot *mm_slot;
> struct mm_slot *slot;
> - int needs_wakeup;
> + bool needs_wakeup;
Unrelated change that should not be included here.
>
> mm_slot = mm_slot_alloc(mm_slot_cache);
> if (!mm_slot)
> @@ -3027,10 +3027,9 @@ int __ksm_enter(struct mm_struct *mm)
>
> slot = &mm_slot->slot;
>
> + spin_lock(&ksm_mmlist_lock);
> /* Check ksm_run too? Would need tighter locking */
> needs_wakeup = list_empty(&ksm_mm_head.slot.mm_node);
> -
> - spin_lock(&ksm_mmlist_lock);
> mm_slot_insert(mm_slots_hash, mm, slot);
> /*
> * When KSM_RUN_MERGE (or KSM_RUN_STOP),
Makes sense to me. With the above variable change removed:
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-08-05 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 15:21 [PATCH 1/1] mm/ksm: avoid missing ksmd wakeups in ksm_enter Longlong Xia
2026-08-05 12:26 ` David Hildenbrand (Arm) [this message]
2026-08-05 13:31 ` Longlong Xia
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=6bb83027-07fb-4152-8edd-f349e6fbcc42@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hugh.dickins@tiscali.co.uk \
--cc=ieidus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xialonglong2025@163.com \
--cc=xialonglong@kylinos.cn \
--cc=xu.xin16@zte.com.cn \
/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