From: Miaohe Lin <linmiaohe@huawei.com>
To: Michal Hocko <mhocko@suse.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] mm/mempolicy: fix potential mpol_new leak in shared_policy_replace
Date: Tue, 15 Mar 2022 21:42:29 +0800 [thread overview]
Message-ID: <26577566-ae1e-801c-8c64-89c2c89a487d@huawei.com> (raw)
In-Reply-To: <Yi9w7TCYbj+OLGXJ@dhcp22.suse.cz>
On 2022/3/15 0:44, Michal Hocko wrote:
> On Fri 11-03-22 17:36:24, 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.
>
> The code is really hideous but is there really any bug there? AFAICS the
> new policy is only allocated in if (n->end > end) branch and that one
> will set the reference count on the retry. Or am I missing something?
>
Many thanks for your comment.
IIUC, new policy is allocated via the below code:
shared_policy_replace:
alloc_new:
write_unlock(&sp->lock);
ret = -ENOMEM;
n_new = kmem_cache_alloc(sn_cache, GFP_KERNEL);
if (!n_new)
goto err_out;
mpol_new = kmem_cache_alloc(policy_cache, GFP_KERNEL);
if (!mpol_new)
goto err_out;
goto restart;
And mpol_new' reference count will be set before used in n->end > end case. But
if that is "not" the case, i.e. mpol_new is not inserted into the rb_tree, mpol_new
will be freed via mpol_put before return:
shared_policy_replace:
err_out:
if (mpol_new)
mpol_put(mpol_new);
if (n_new)
kmem_cache_free(sn_cache, n_new);
But mpol_new' reference count is not set yet, we have trouble now.
Does this makes sense for you? Or am I miss something?
Thanks.
>> Fixes: 42288fe366c4 ("mm: mempolicy: Convert shared_policy mutex to spinlock")
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>> mm/mempolicy.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
>> index 34d2b29c96ad..f19f19d3558b 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
>
next prev parent reply other threads:[~2022-03-15 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 9:36 Miaohe Lin
2022-03-14 16:44 ` Michal Hocko
2022-03-15 13:42 ` Miaohe Lin [this message]
2022-03-15 15:27 ` Michal Hocko
2022-03-16 6:39 ` Miaohe Lin
2022-03-16 9:56 ` Michal Hocko
2022-03-17 2:05 ` Miaohe Lin
2022-03-17 9:03 ` Michal Hocko
2022-03-17 9:34 ` Miaohe Lin
2022-03-19 10:42 ` Miaohe Lin
2022-03-21 8:59 ` Michal Hocko
2022-03-21 9:25 ` 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=26577566-ae1e-801c-8c64-89c2c89a487d@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.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