From: Jinjiang Tu <tujinjiang@huawei.com>
To: <akpm@linux-foundation.org>, <david@redhat.com>,
<shr@devkernel.io>, <hannes@cmpxchg.org>, <riel@surriel.com>,
<wangkefeng.wang@huawei.com>, <sunnanyong@huawei.com>,
<linux-mm@kvack.org>
Subject: Re: [PATCH v3] mm/ksm: fix ksm exec support for prctl
Date: Mon, 18 Mar 2024 16:19:31 +0800 [thread overview]
Message-ID: <a6e09f17-40b9-1e49-19da-d0165b0ac33d@huawei.com> (raw)
In-Reply-To: <20240318090441.179486-1-tujinjiang@huawei.com>
Sorry, the v3 tag is erroneous. This patch is the first version.
在 2024/3/18 17:04, Jinjiang Tu 写道:
> commit 3c6f33b7273a ("mm/ksm: support fork/exec for prctl") inherits
> MMF_VM_MERGE_ANY flag when a task calls execve(). Howerver, it doesn't
> create the mm_slot, so ksmd will not try to scan this task.
>
> To fix it, allocate and add the mm_slot to ksm_mm_head in __bprm_mm_init()
> when the mm has MMF_VM_MERGE_ANY flag.
>
> Fixes: 3c6f33b7273a ("mm/ksm: support fork/exec for prctl")
> Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>
> ---
> fs/exec.c | 4 ++++
> include/linux/ksm.h | 13 +++++++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/fs/exec.c b/fs/exec.c
> index ff6f26671cfc..00f40163cc12 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -67,6 +67,7 @@
> #include <linux/time_namespace.h>
> #include <linux/user_events.h>
> #include <linux/rseq.h>
> +#include <linux/ksm.h>
>
> #include <linux/uaccess.h>
> #include <asm/mmu_context.h>
> @@ -267,6 +268,9 @@ static int __bprm_mm_init(struct linux_binprm *bprm)
> goto err_free;
> }
>
> + if (ksm_execve(mm))
> + goto err;
> +
> /*
> * Place the stack at the largest stack address the architecture
> * supports. Later, we'll move this to an appropriate place. We don't
> diff --git a/include/linux/ksm.h b/include/linux/ksm.h
> index 401348e9f92b..7e2b1de3996a 100644
> --- a/include/linux/ksm.h
> +++ b/include/linux/ksm.h
> @@ -59,6 +59,14 @@ static inline int ksm_fork(struct mm_struct *mm, struct mm_struct *oldmm)
> return 0;
> }
>
> +static inline int ksm_execve(struct mm_struct *mm)
> +{
> + if (test_bit(MMF_VM_MERGE_ANY, &mm->flags))
> + return __ksm_enter(mm);
> +
> + return 0;
> +}
> +
> static inline void ksm_exit(struct mm_struct *mm)
> {
> if (test_bit(MMF_VM_MERGEABLE, &mm->flags))
> @@ -107,6 +115,11 @@ static inline int ksm_fork(struct mm_struct *mm, struct mm_struct *oldmm)
> return 0;
> }
>
> +static inline int ksm_execve(struct mm_struct *mm)
> +{
> + return 0;
> +}
> +
> static inline void ksm_exit(struct mm_struct *mm)
> {
> }
next prev parent reply other threads:[~2024-03-18 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:04 [PATCH v3] mm/ksm: fix ksm exec support for prctl Jinjiang Tu
2024-03-18 8:19 ` Jinjiang Tu [this message]
2024-03-18 9:36 ` David Hildenbrand
2024-03-18 10:52 ` Jinjiang Tu
2024-03-18 10:54 ` David Hildenbrand
2024-03-18 9:59 ` David Hildenbrand
2024-03-18 10:54 ` 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=a6e09f17-40b9-1e49-19da-d0165b0ac33d@huawei.com \
--to=tujinjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=shr@devkernel.io \
--cc=sunnanyong@huawei.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).