From: Zach O'Keefe <zokeefe@google.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] mm/khugepaged: Avoid possible memory leak in failure path
Date: Wed, 13 Jul 2022 09:39:27 -0700 [thread overview]
Message-ID: <Ys71P4AsGkzmoRQh@google.com> (raw)
In-Reply-To: <20220713024109.62810-1-jrdr.linux@gmail.com>
On Jul 13 08:11, Souptick Joarder wrote:
> From: "Souptick Joarder (HPE)" <jrdr.linux@gmail.com>
>
> smatch warnings:
> mm/khugepaged.c:2409 madvise_collapse() warn: possible memory
> leak of 'cc'
>
> Avoiding possible memory leak.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Souptick Joarder (HPE) <jrdr.linux@gmail.com>
> ---
> mm/khugepaged.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 0207fc0a5b2a..8da9e7467543 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -2397,12 +2397,6 @@ int madvise_collapse(struct vm_area_struct *vma, struct vm_area_struct **prev,
> BUG_ON(vma->vm_start > start);
> BUG_ON(vma->vm_end < end);
>
> - cc = kmalloc(sizeof(*cc), GFP_KERNEL);
> - if (!cc)
> - return -ENOMEM;
> - cc->is_khugepaged = false;
> - cc->last_target_node = NUMA_NO_NODE;
> -
> *prev = vma;
>
> /* TODO: Support file/shmem */
> @@ -2415,6 +2409,12 @@ int madvise_collapse(struct vm_area_struct *vma, struct vm_area_struct **prev,
> if (!hugepage_vma_check(vma, vma->vm_flags, false, false, false))
> return -EINVAL;
>
> + cc = kmalloc(sizeof(*cc), GFP_KERNEL);
> + if (!cc)
> + return -ENOMEM;
> + cc->is_khugepaged = false;
> + cc->last_target_node = NUMA_NO_NODE;
> +
> mmgrab(mm);
> lru_add_drain_all();
>
> --
> 2.25.1
>
>
Thanks for the fix!
I've also sent out another patch on top which addresses the actual missing
kfree()
prev parent reply other threads:[~2022-07-13 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 2:41 Souptick Joarder
2022-07-13 16:39 ` Zach O'Keefe [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=Ys71P4AsGkzmoRQh@google.com \
--to=zokeefe@google.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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