From: David Hildenbrand <david@redhat.com>
To: Kiryl Shutsemau <kirill@shutemov.name>,
Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, 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,
linux-mm@kvack.org, Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [Patch v3 1/2] mm/ksm: get mm_slot by mm_slot_entry() when slot is !NULL
Date: Wed, 24 Sep 2025 11:40:21 +0200 [thread overview]
Message-ID: <1ebbfe02-1cb5-4f7a-a640-68d5d95cb99b@redhat.com> (raw)
In-Reply-To: <27storxu4seijr5smul3xx7pofe45ittjrchii3jtwbntalsiy@2cu3wf42drwa>
On 24.09.25 11:35, Kiryl Shutsemau wrote:
> On Wed, Sep 24, 2025 at 12:48:53AM +0000, Wei Yang wrote:
>> Patch series "mm_slot: fix the usage of mm_slot_entry", v2.
>>
>> 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, access mm_slot_entry() when
>> slot is !NULL.
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> Acked-by: David Hildenbrand <david@redhat.com>
>> Reviewed-by: Dev Jain <dev.jain@arm.com>
>> Reviewed-by: 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>
>>
>> ---
>> v3:
>> * fix uninitialized mm_slot
>> ---
>> mm/ksm.c | 22 ++++++++++++----------
>> 1 file changed, 12 insertions(+), 10 deletions(-)
>>
>> diff --git a/mm/ksm.c b/mm/ksm.c
>> index 2dbe92e3dd52..c00a21800067 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,15 +2936,17 @@ void __ksm_exit(struct mm_struct *mm)
>>
>> spin_lock(&ksm_mmlist_lock);
>> slot = mm_slot_lookup(mm_slots_hash, mm);
>> - 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 (slot) {
>> + mm_slot = mm_slot_entry(slot, struct ksm_mm_slot, slot);
>> + if (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);
>> + }
>
> Indent level gets extreme.
You call this extreme? :)
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-09-24 9:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 0:48 [Patch v3 0/2] mm_slot: fix the usage of mm_slot_entry Wei Yang
2025-09-24 0:48 ` [Patch v3 1/2] mm/ksm: get mm_slot by mm_slot_entry() when slot is !NULL Wei Yang
2025-09-24 2:19 ` Chengming Zhou
2025-09-24 9:35 ` Kiryl Shutsemau
2025-09-24 9:40 ` David Hildenbrand [this message]
2025-09-24 10:06 ` Kiryl Shutsemau
2025-09-24 10:09 ` David Hildenbrand
2025-09-24 10:15 ` Kiryl Shutsemau
2025-09-24 10:42 ` David Hildenbrand
2025-09-24 14:52 ` Wei Yang
2025-09-24 9:35 ` David Hildenbrand
2025-09-24 0:48 ` [Patch v3 2/2] mm/khugepaged: remove definition of struct khugepaged_mm_slot Wei Yang
2025-09-24 3:18 ` Lance Yang
2025-09-24 5:51 ` Dev Jain
2025-09-24 9:39 ` David Hildenbrand
2025-09-24 14:59 ` Wei Yang
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=1ebbfe02-1cb5-4f7a-a640-68d5d95cb99b@redhat.com \
--to=david@redhat.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=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