From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>,
Austin Kim <austindh.kim@gmail.com>
Cc: urezki@gmail.com, guro@fb.com, rpenyaev@suse.de, mhocko@suse.com,
rick.p.edgecombe@intel.com, rppt@linux.ibm.com,
aryabinin@virtuozzo.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc: move 'area->pages' after if statement
Date: Mon, 2 Sep 2019 16:15:55 +0200 [thread overview]
Message-ID: <8d537e02-9479-d3b2-f74a-7136f03ecde2@suse.cz> (raw)
In-Reply-To: <20190830135007.8b5949bd57975d687ff0a3f8@linux-foundation.org>
On 8/30/19 10:50 PM, Andrew Morton wrote:
> On Fri, 30 Aug 2019 12:57:16 +0900 Austin Kim <austindh.kim@gmail.com> wrote:
>
>> If !area->pages statement is true where memory allocation fails,
>> area is freed.
>>
>> In this case 'area->pages = pages' should not executed.
That read like a use after free fix and made me wonder about stable,
fixes etc... luckily it's not.
>> So move 'area->pages = pages' after if statement.
>>
>> ...
>>
>> --- a/mm/vmalloc.c
>> +++ b/mm/vmalloc.c
>> @@ -2416,13 +2416,15 @@ static void *__vmalloc_area_node(struct vm_struct *area, gfp_t gfp_mask,
>> } else {
>> pages = kmalloc_node(array_size, nested_gfp, node);
>> }
>> - area->pages = pages;
>> - if (!area->pages) {
>> +
>> + if (!pages) {
>> remove_vm_area(area->addr);
>> kfree(area);
>> return NULL;
>> }
>>
>> + area->pages = pages;
>> +
>> for (i = 0; i < area->nr_pages; i++) {
>> struct page *page;
>>
>
> Fair enough. But we can/should also do this?
Agreed, same thing.
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> --- a/mm/vmalloc.c~mm-vmalloc-move-area-pages-after-if-statement-fix
> +++ a/mm/vmalloc.c
> @@ -2409,7 +2409,6 @@ static void *__vmalloc_area_node(struct
> nr_pages = get_vm_area_size(area) >> PAGE_SHIFT;
> array_size = (nr_pages * sizeof(struct page *));
>
> - area->nr_pages = nr_pages;
> /* Please note that the recursion is strictly bounded. */
> if (array_size > PAGE_SIZE) {
> pages = __vmalloc_node(array_size, 1, nested_gfp|highmem_mask,
> @@ -2425,6 +2424,7 @@ static void *__vmalloc_area_node(struct
> }
>
> area->pages = pages;
> + area->nr_pages = nr_pages;
>
> for (i = 0; i < area->nr_pages; i++) {
> struct page *page;
> _
>
>
next prev parent reply other threads:[~2019-09-02 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 3:57 Austin Kim
2019-08-30 5:38 ` Michal Hocko
2019-08-30 20:50 ` Andrew Morton
2019-09-02 14:15 ` Vlastimil Babka [this message]
2019-09-02 21:28 ` Austin Kim
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=8d537e02-9479-d3b2-f74a-7136f03ecde2@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=austindh.kim@gmail.com \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rick.p.edgecombe@intel.com \
--cc=rpenyaev@suse.de \
--cc=rppt@linux.ibm.com \
--cc=urezki@gmail.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