From: Liam Howlett <liam.howlett@oracle.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"willy@infradead.org" <willy@infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"vbabka@suse.cz" <vbabka@suse.cz>
Subject: Re: [PATCH -next] mm/nommu: fix error handling in split_vma()
Date: Wed, 24 Aug 2022 14:47:11 +0000 [thread overview]
Message-ID: <20220824144703.gwr45mmdk6xl73my@revolver> (raw)
In-Reply-To: <20220824042424.2031508-1-yangyingliang@huawei.com>
Thanks. This is a valid issue and a good fix.
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
* Yang Yingliang <yangyingliang@huawei.com> [220824 00:16]:
> The memory allocated before calling mas_preallocate() is leaked if it fails.
> 'mas' won't be modify until calling mas_preallocate(), so move it up and
> add error label for free the memory.
>
> Fixes: 8aff7dbeaeb1 ("nommu: remove uses of VMA linked list")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> mm/nommu.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 6c611a689ec0..214c70e1d059 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -1355,9 +1355,13 @@ int split_vma(struct mm_struct *mm, struct vm_area_struct *vma,
> return -ENOMEM;
>
> new = vm_area_dup(vma);
> - if (!new) {
> - kmem_cache_free(vm_region_jar, region);
> - return -ENOMEM;
> + if (!new)
> + goto err_vma_dup;
> +
> + if (mas_preallocate(&mas, vma, GFP_KERNEL)) {
> + pr_warn("Allocation of vma tree for process %d failed\n",
> + current->pid);
> + goto err_mas_preallocate;
> }
>
> /* most fields are the same, copy all, and then fixup */
> @@ -1388,11 +1392,6 @@ int split_vma(struct mm_struct *mm, struct vm_area_struct *vma,
> add_nommu_region(vma->vm_region);
> add_nommu_region(new->vm_region);
> up_write(&nommu_region_sem);
> - if (mas_preallocate(&mas, vma, GFP_KERNEL)) {
> - pr_warn("Allocation of vma tree for process %d failed\n",
> - current->pid);
> - return -ENOMEM;
> - }
>
> setup_vma_to_mm(vma, mm);
> setup_vma_to_mm(new, mm);
> @@ -1400,6 +1399,12 @@ int split_vma(struct mm_struct *mm, struct vm_area_struct *vma,
> mas_store(&mas, vma);
> vma_mas_store(new, &mas);
> return 0;
> +
> +err_mas_preallocate:
> + vm_area_free(new);
> +err_vma_dup:
> + kmem_cache_free(vm_region_jar, region);
> + return -ENOMEM;
> }
>
> /*
> --
> 2.25.1
>
prev parent reply other threads:[~2022-08-24 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 4:24 Yang Yingliang
2022-08-24 14:47 ` Liam Howlett [this message]
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=20220824144703.gwr45mmdk6xl73my@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yangyingliang@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