From: Muhammad Usama Anjum <MUsamaAnjum@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, david@redhat.com,
lorenzo.stoakes@oracle.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, xu.xin16@zte.com.cn,
chengming.zhou@linux.dev
Cc: linux-mm@kvack.org, Kiryl Shutsemau <kirill@shutemov.name>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [Patch v4 1/2] mm/ksm: don't call mm_slot_entry() when the slot is NULL
Date: Sat, 27 Sep 2025 13:39:36 +0500 [thread overview]
Message-ID: <f82d2bac-9e8d-4baa-af50-a4f6ed3e0c13@gmail.com> (raw)
In-Reply-To: <20250927004539.19308-2-richard.weiyang@gmail.com>
On 9/27/25 5:45 AM, Wei Yang wrote:
> When using mm_slot in ksm, there is code like:
>
> slot = mm_slot_lookup(mm_slots_hash, mm);
> mm_slot = mm_slot_entry(slot, struct ksm_mm_slot, slot);
> if (mm_slot && ..) {
> }
>
> The mm_slot_entry() won't return a valid value if slot is NULL generally.
> But currently it works since slot is the first element of struct
> ksm_mm_slot.
>
> To reduce the ambiguity and make it robust, only call mm_slot_entry()
> when we have a valid slot.
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Dev Jain <dev.jain@arm.com>
> Cc: Lance Yang <lance.yang@linux.dev>
> Cc: Kiryl Shutsemau <kirill@shutemov.name>
> Cc: xu xin <xu.xin16@zte.com.cn>
> Cc: Dan Carpenter <dan.carpenter@linaro.org>
> Cc: Chengming Zhou <chengming.zhou@linux.dev>
Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
>
> ---
> v3:
> * adjust subject and changelog based on David's comment
> * use invert style for coding suggested by Kiryl
> * drop RB and Ack-by
> v2:
> * fix uninitialized mm_slot
> ---
> mm/ksm.c | 23 +++++++++++++----------
> 1 file changed, 13 insertions(+), 10 deletions(-)
>
> diff --git a/mm/ksm.c b/mm/ksm.c
> index 2dbe92e3dd52..7bc726b50b2f 100644
> --- a/mm/ksm.c
> +++ b/mm/ksm.c
> @@ -2921,7 +2921,7 @@ int __ksm_enter(struct mm_struct *mm)
>
> void __ksm_exit(struct mm_struct *mm)
> {
> - struct ksm_mm_slot *mm_slot;
> + struct ksm_mm_slot *mm_slot = NULL;
> struct mm_slot *slot;
> int easy_to_free = 0;
>
> @@ -2936,17 +2936,20 @@ void __ksm_exit(struct mm_struct *mm)
>
> spin_lock(&ksm_mmlist_lock);
> slot = mm_slot_lookup(mm_slots_hash, mm);
> + if (!slot)
> + goto unlock;
> mm_slot = mm_slot_entry(slot, struct ksm_mm_slot, slot);
> - if (mm_slot && ksm_scan.mm_slot != mm_slot) {
> - if (!mm_slot->rmap_list) {
> - hash_del(&slot->hash);
> - list_del(&slot->mm_node);
> - easy_to_free = 1;
> - } else {
> - list_move(&slot->mm_node,
> - &ksm_scan.mm_slot->slot.mm_node);
> - }
> + if (ksm_scan.mm_slot == mm_slot)
> + goto unlock;
> + if (!mm_slot->rmap_list) {
> + hash_del(&slot->hash);
> + list_del(&slot->mm_node);
> + easy_to_free = 1;
> + } else {
> + list_move(&slot->mm_node,
> + &ksm_scan.mm_slot->slot.mm_node);
> }
> +unlock:
> spin_unlock(&ksm_mmlist_lock);
>
> if (easy_to_free) {
next prev parent reply other threads:[~2025-09-27 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 0:45 [Patch v4 0/2] mm_slot: fix the usage of mm_slot_entry() Wei Yang
2025-09-27 0:45 ` [Patch v4 1/2] mm/ksm: don't call mm_slot_entry() when the slot is NULL Wei Yang
2025-09-27 8:39 ` Muhammad Usama Anjum [this message]
2025-09-28 13:53 ` Dev Jain
2025-09-29 8:13 ` David Hildenbrand
2025-09-29 10:58 ` Kiryl Shutsemau
2025-09-29 15:14 ` Zi Yan
2025-09-27 0:45 ` [Patch v4 2/2] mm/khugepaged: remove definition of struct khugepaged_mm_slot Wei Yang
2025-09-27 8:40 ` Muhammad Usama Anjum
2025-09-29 8:13 ` David Hildenbrand
2025-09-29 15:16 ` Zi Yan
2025-09-30 6:01 ` Raghavendra K T
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=f82d2bac-9e8d-4baa-af50-a4f6ed3e0c13@gmail.com \
--to=musamaanjum@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chengming.zhou@linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=kirill@shutemov.name \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=xu.xin16@zte.com.cn \
--cc=ziy@nvidia.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