From: Michal Hocko <mhocko@suse.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com,
mgorman@suse.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/mempolicy: fix mpol_new leak in shared_policy_replace
Date: Mon, 21 Mar 2022 13:12:00 +0100 [thread overview]
Message-ID: <YjhrkDlvOnmqIP6n@dhcp22.suse.cz> (raw)
In-Reply-To: <20220322083456.16563-1-linmiaohe@huawei.com>
On Tue 22-03-22 16:34:56, Miaohe Lin wrote:
> If mpol_new is allocated but not used in restart loop, mpol_new will be
> freed via mpol_put before returning to the caller. But refcnt is not
> initialized yet, so mpol_put could not do the right things and might leak
> the unused mpol_new.
I would just add:
This would happen if mempolicy was updated on the shared shmem file
while the sp->lock has been dropped during the memory allocation.
> This issue could be triggered easily with the below
> code snippet if there're many processes doing the below work at the same
> time:
>
> shmid = shmget((key_t)5566, 1024 * PAGE_SIZE, 0666|IPC_CREAT);
> shm = shmat(shmid, 0, 0);
> loop many times {
> mbind(shm, 1024 * PAGE_SIZE, MPOL_LOCAL, mask, maxnode, 0);
> mbind(shm + 128 * PAGE_SIZE, 128 * PAGE_SIZE, MPOL_DEFAULT, mask,
> maxnode, 0);
> }
>
> Fixes: 42288fe366c4 ("mm: mempolicy: Convert shared_policy mutex to spinlock")
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> Cc: <stable@vger.kernel.org> # 3.8
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks a lot!
> ---
> v1->v2:
> Add reproducer snippet and Cc stable.
> Thanks Michal Hocko for review and comment!
> ---
> mm/mempolicy.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index a2516d31db6c..4cdd425b2752 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -2733,6 +2733,7 @@ static int shared_policy_replace(struct shared_policy *sp, unsigned long start,
> mpol_new = kmem_cache_alloc(policy_cache, GFP_KERNEL);
> if (!mpol_new)
> goto err_out;
> + refcount_set(&mpol_new->refcnt, 1);
> goto restart;
> }
>
> --
> 2.23.0
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-03-21 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:34 Miaohe Lin
2022-03-21 12:12 ` Michal Hocko [this message]
2022-03-22 1:50 ` Miaohe Lin
2022-03-22 8:08 ` Michal Hocko
2022-03-21 18:29 ` kernel test robot
2022-03-21 20:01 ` kernel test robot
2022-03-22 2:16 ` Miaohe Lin
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=YjhrkDlvOnmqIP6n@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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