linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave@sr71.net>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Jan Beulich <JBeulich@novell.com>,
	Christoph Lameter <cl@linux.com>, linux-mm <linux-mm@kvack.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUILD_BUG_ON() breaks sparse gfp_t checks
Date: Thu, 14 Apr 2011 13:22:20 -0700	[thread overview]
Message-ID: <20110414132220.970cfb2a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1302795695.14658.6801.camel@nimitz>

On Thu, 14 Apr 2011 08:41:35 -0700
Dave Hansen <dave@sr71.net> wrote:

> Running sparse on page_alloc.c today, it errors out:
>         
>         mm/page_alloc.c:96:5: warning: symbol 'percpu_pagelist_fraction' was not declared. Should it be static?
>         mm/page_alloc.c:175:5: warning: symbol 'min_free_kbytes' was not declared. Should it be static?
>         include/linux/gfp.h:254:17: error: bad constant expression
>         include/linux/gfp.h:254:17: error: cannot size expression
> 
> which is a line in gfp_zone():
> 
> 	BUILD_BUG_ON((GFP_ZONE_BAD >> bit) & 1);
> 
> That's really unfortunate, because it ends up hiding all of the other
> legitimate sparse messages (like I introduced with the appended patch):
> 
>         mm/page_alloc.c:96:5: warning: symbol 'percpu_pagelist_fraction' was not declared. Should it be static?
>         mm/page_alloc.c:175:5: warning: symbol 'min_free_kbytes' was not declared. Should it be static?
>         mm/page_alloc.c:3692:15: warning: symbol '__early_pfn_to_nid' was not declared. Should it be static?
>         mm/page_alloc.c:5315:59: warning: incorrect type in argument 1 (different base types)
>         mm/page_alloc.c:5315:59:    expected unsigned long [unsigned] [usertype] size
>         mm/page_alloc.c:5315:59:    got restricted gfp_t [usertype] <noident>
> ...
> 
> Is sparse broken, or is that ?  Even if it is, should we be working
> around this somehow?  It looks like we've basically crippled sparse in
> some spots.

Is sparse having conniptions over that monster expression for
GFP_ZONE_BAD?

The kernel calls gfp_zone() with a constant arg in very few places. 
This?

--- a/include/linux/gfp.h~a
+++ a/include/linux/gfp.h
@@ -249,14 +249,9 @@ static inline enum zone_type gfp_zone(gf
 
 	z = (GFP_ZONE_TABLE >> (bit * ZONES_SHIFT)) &
 					 ((1 << ZONES_SHIFT) - 1);
-
-	if (__builtin_constant_p(bit))
-		BUILD_BUG_ON((GFP_ZONE_BAD >> bit) & 1);
-	else {
 #ifdef CONFIG_DEBUG_VM
-		BUG_ON((GFP_ZONE_BAD >> bit) & 1);
+	BUG_ON((GFP_ZONE_BAD >> bit) & 1);
 #endif
-	}
 	return z;
 }
 
_

--
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-04-14 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 15:41 Dave Hansen
2011-04-14 20:22 ` Andrew Morton [this message]
2011-04-14 21:39   ` Dave Hansen
2011-04-15 14:45     ` Christoph Lameter
2011-04-15 19:16       ` [PATCH] make new gfp.h BUG_ON() in to VM_BUG_ON() Dave Hansen

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=20110414132220.970cfb2a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=JBeulich@novell.com \
    --cc=cl@linux.com \
    --cc=dave@sr71.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rusty@rustcorp.com.au \
    /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