linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Akinobu Mita <akinobu.mita@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: add gfp mask checking for __get_free_pages()
Date: Sat, 18 Jul 2009 10:29:44 +0900	[thread overview]
Message-ID: <961aa3350907171829i52c095aam610ae2dc3d931080@mail.gmail.com> (raw)
In-Reply-To: <20090717174128.36d00972.akpm@linux-foundation.org>

2009/7/18 Andrew Morton <akpm@linux-foundation.org>:
> On Sat, 4 Jul 2009 11:09:50 +0900
> Akinobu Mita <akinobu.mita@gmail.com> wrote:
>
>> __get_free_pages() with __GFP_HIGHMEM is not safe because the return
>> address cannot represent a highmem page. get_zeroed_page() already has
>> such a debug checking.
>>
>> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
>> ---
>>  mm/page_alloc.c |   24 +++++++++---------------
>>  1 files changed, 9 insertions(+), 15 deletions(-)
>>
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index e0f2cdf..4a1a374 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -1903,31 +1903,25 @@ EXPORT_SYMBOL(__alloc_pages_nodemask);
>>   */
>>  unsigned long __get_free_pages(gfp_t gfp_mask, unsigned int order)
>>  {
>> -     struct page * page;
>> +     struct page *page;
>> +
>> +     /*
>> +      * __get_free_pages() returns a 32-bit address, which cannot represent
>> +      * a highmem page
>> +      */
>> +     VM_BUG_ON((gfp_mask & __GFP_HIGHMEM) != 0);
>> +
>>       page = alloc_pages(gfp_mask, order);
>>       if (!page)
>>               return 0;
>>       return (unsigned long) page_address(page);
>>  }
>> -
>>  EXPORT_SYMBOL(__get_free_pages);
>>
>>  unsigned long get_zeroed_page(gfp_t gfp_mask)
>>  {
>> -     struct page * page;
>> -
>> -     /*
>> -      * get_zeroed_page() returns a 32-bit address, which cannot represent
>> -      * a highmem page
>> -      */
>> -     VM_BUG_ON((gfp_mask & __GFP_HIGHMEM) != 0);
>> -
>> -     page = alloc_pages(gfp_mask | __GFP_ZERO, 0);
>> -     if (page)
>> -             return (unsigned long) page_address(page);
>> -     return 0;
>> +     return __get_free_pages(gfp_mask | __GFP_ZERO, 0);
>>  }
>> -
>>  EXPORT_SYMBOL(get_zeroed_page);
>>
>>  void __pagevec_free(struct pagevec *pvec)
>
> Fair enough.
>
> I suspect we could just delete that VM_BUG_ON() - we can't go and do
> runtime checking for every darn programmer error, and this would be a
> pretty dumb one.

Maybe. But we had such a bug in c51b1a160b63304720d49479986915e4c475a2cf
(xip: fix get_zeroed_page with __GFP_HIGHME). Even the VM code
had it and did not fixed for a long time.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2009-07-18  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090704020949.GA3047@localhost.localdomain>
2009-07-18  0:41 ` [PATCH] mm: add gfp mask checking for __get_free_pages() Andrew Morton
2009-07-18  1:29   ` Akinobu Mita [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=961aa3350907171829i52c095aam610ae2dc3d931080@mail.gmail.com \
    --to=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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).