linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Rik van Riel <riel@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	linux-mm@kvack.org
Subject: Re: [patch] mm: fail GFP_DMA allocations when ZONE_DMA is not configured
Date: Wed, 4 May 2011 12:33:35 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1105041219130.22426@chino.kir.corp.google.com> (raw)
In-Reply-To: <20110414145458.f9bb7744.akpm@linux-foundation.org>

On Thu, 14 Apr 2011, Andrew Morton wrote:

> > The page allocator will improperly return a page from ZONE_NORMAL even 
> > when __GFP_DMA is passed if CONFIG_ZONE_DMA is disabled.  The caller 
> > expects DMA memory, perhaps for ISA devices with 16-bit address 
> > registers, and may get higher memory resulting in undefined behavior.
> > 
> > This patch causes the page allocator to return NULL in such circumstances 
> > with a warning emitted to the kernel log on the first occurrence.
> > 
> > Signed-off-by: David Rientjes <rientjes@google.com>
> > ---
> >  mm/page_alloc.c |    4 ++++
> >  1 files changed, 4 insertions(+), 0 deletions(-)
> > 
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -2225,6 +2225,10 @@ __alloc_pages_nodemask(gfp_t gfp_mask, unsigned int order,
> >  
> >  	if (should_fail_alloc_page(gfp_mask, order))
> >  		return NULL;
> > +#ifndef CONFIG_ZONE_DMA
> > +	if (WARN_ON_ONCE(gfp_mask & __GFP_DMA))
> > +		return NULL;
> > +#endif
> 
> Worried.  We have a large number of drivers which use GFP_DMA and I bet
> some of them didn't really need to set it, and can use DMA32 memory. 
> They will now break.
> 

They were already broken for CONFIG_ZONE_DMA=n since passing __GFP_DMA 
never guaranteed the memory came from ZONE_DMA32 (and would return 
ZONE_NORMAL memory even if CONFIG_ZONE_DMA32=n).

> What is drivers/pci/intel-iommu.c doing with GFP_DMA btw?
> 

Looks like if no identity mapping is needed for that device (using a 
non-identity mapping instead), then there is no lowmem restriction on its 
allocation; otherwise, we use lowmem is used when the device's mask 
specifically requires it.

Adding Alex and David to the cc.

> How commonly are people disabling ZONE_DMA?
> 

Probably not that much, it's usually def_bool y everywhere and just 
implicitly on.  I'm changing that for x86 on a CONFIG_EXPERT kernel so 
that we can avoid a ZONE_DMA entirely; that prevents reserving memory we 
don't need with the lowmem reserve by default, we can eliminate the DMA 
slab caches, etc.  Google has been running with CONFIG_ZONE_DMA=n for a 
couple years because we simply don't need it.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2011-05-04 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 21:46 David Rientjes
2011-04-14 21:54 ` Andrew Morton
2011-05-04 19:33   ` David Rientjes [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=alpine.DEB.2.00.1105041219130.22426@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=David.Woodhouse@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=riel@redhat.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