linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc.c: Fix potential memory leak
Date: Thu, 7 Jan 2021 14:14:11 +0100	[thread overview]
Message-ID: <20210107131411.GA2053@pc638.lan> (raw)
In-Reply-To: <20210107123541.39206-1-linmiaohe@huawei.com>

> In VM_MAP_PUT_PAGES case, we should put pages and free array in vfree. But
> we missed to set area->nr_pages in vmap(). So we would failed to put pages
> in __vunmap() because area->nr_pages = 0.
> 
> Fixes: b944afc9d64d ("mm: add a VM_MAP_PUT_PAGES flag for vmap")
> Signed-off-by: Shijie Luo <luoshijie1@huawei.com>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> Cc: <stable@vger.kernel.org>
> ---
>  mm/vmalloc.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 6507a579ff88..8ab83fbecadd 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2421,8 +2421,10 @@ void *vmap(struct page **pages, unsigned int count,
>  		return NULL;
>  	}
>  
> -	if (flags & VM_MAP_PUT_PAGES)
> +	if (flags & VM_MAP_PUT_PAGES) {
>  		area->pages = pages;
> +		area->nr_pages = count;
> +	}
>  	return area->addr;
>  }
>  EXPORT_SYMBOL(vmap);
> -- 
> 2.19.1
> 
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>

--
Vlad Rezki


      reply	other threads:[~2021-01-07 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 12:35 [PATCH] mm/vmalloc.c: Fix potential memory leak Miaohe Lin
2021-01-07 13:14 ` Uladzislau Rezki [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=20210107131411.GA2053@pc638.lan \
    --to=urezki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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).