From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Jinjiang Tu <tujinjiang@huawei.com>,
akpm@linux-foundation.org, xu.xin@linux.dev,
chengming.zhou@linux.dev, liam@infradead.org, ljs@kernel.org,
vbabka@kernel.org, jannh@google.com, pfalcato@suse.de,
kees@kernel.org, ziy@nvidia.com, gourry@gourry.net,
anthony.yznaga@oracle.com, linux-mm@kvack.org
Cc: wangkefeng.wang@huawei.com, sunnanyong@huawei.com
Subject: Re: [PATCH] mm/ksm: fix ksm_exit() deadlock on exec error path
Date: Sat, 7 Nov 2026 20:06:55 +0100 [thread overview]
Message-ID: <a712518e-e094-474a-b7c3-bb9723917960@kernel.org> (raw)
In-Reply-To: <20261106013906.2229780-1-tujinjiang@huawei.com>
On 11/6/26 02:39, Jinjiang Tu wrote:
> create_init_stack_vma() registers the new mm with ksmd via ksm_execve()
> while holding mmap_write_lock(), and calls ksm_exit() before dropping the
> lock. When insert_vm_struct() fails, __ksm_exit() takes mmap_write_lock()
> again when the mm is ksmd's current scan cursor, leading to deadlock.
>
> The early registration is no longer needed after commit 590c03ca6a3f
> ("mm/ksm: fix exec/fork inheritance support for prctl"). ksm_vma_flags()
> calls __ksm_enter() when the first mergeable VMA is created. Remove
> ksm_execve() and its stubs.
I assume you mean the
} else if (mm_slot) {
mmap_write_lock(mm);
mmap_write_unlock(mm);
}
Can that actually trigger?
IOW, can we have an slot, and the slot can already have a mm_slot->rmap_list?
--
Cheers,
David
next prev parent reply other threads:[~2026-11-07 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:39 [PATCH] mm/ksm: fix ksm_exit() deadlock on exec error path Jinjiang Tu
2026-11-06 8:28 ` Xu Xin (vivo)
2026-11-07 2:48 ` Jinjiang Tu
2026-11-06 8:46 ` Xu Xin (vivo)
2026-11-07 2:56 ` Jinjiang Tu
2026-11-07 19:06 ` David Hildenbrand (Arm) [this message]
2026-11-09 1:53 ` Jinjiang Tu
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=a712518e-e094-474a-b7c3-bb9723917960@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=chengming.zhou@linux.dev \
--cc=gourry@gourry.net \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=sunnanyong@huawei.com \
--cc=tujinjiang@huawei.com \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=xu.xin@linux.dev \
--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