From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>,
dri-devel@lists.freedesktop.org, Dave Airlie <airlied@gmail.com>
Subject: Re: linux-next: Tree for Nov 14 (gpu/drm/i915)
Date: Wed, 14 Nov 2012 12:17:47 -0800 [thread overview]
Message-ID: <20121114121747.46ffe05f.akpm@linux-foundation.org> (raw)
In-Reply-To: <50A3F3FD.4070707@infradead.org>
On Wed, 14 Nov 2012 11:41:49 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 11/13/2012 09:30 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > News: next-20121115 (i.e. tomorrow) will be the last release until
> > next-20121126 (which should be just be after -rc7, I guess - assuming
> > that Linus does not release v3.7 before then), so if you want something
> > in linux-next for a reasonable amount of testing, it should probably be
> > committed tomorrow.
> >
> > Changes since 20121113:
> >
>
>
>
> on i386:
>
> ERROR: "__build_bug_on_failed" [drivers/gpu/drm/i915/i915.ko] undefined!
>
> Reference to that symbol is found in
> i915_gem_execbuffer.o. Reference to BUILD_BUG_ON() is found in
> i915_gem_execbuffer.c:
>
> static struct eb_objects *
> eb_create(int size)
> {
> struct eb_objects *eb;
> int count = PAGE_SIZE / sizeof(struct hlist_head) / 2;
> BUILD_BUG_ON(!is_power_of_2(PAGE_SIZE / sizeof(struct hlist_head)));
>
Where to start.
- eb_create() has no business assuming that the hlist_head has any
particular size. We could easily add some conditionally-compiled
debug fields in there, and drm blows up.
- The assertion is obviously true at present, so I assume that gcc
screwed up and failed to reduce all that to a compile-time constant.
- We have a BUILD_BUG_ON_NOT_POWER_OF_2(). Use it?
- This code is using PAGE_SIZE to scale a kernel data structure.
PAGE_SIZE can vary by a factor of 16, depending on Kconfig. This
can result in 64k PAGE_SIZE machines exhibiting different beahviour
from that which the testers saw.
Don't do it. It's better to hard-wire 4096.
next prev parent reply other threads:[~2012-11-14 20:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 5:30 linux-next: Tree for Nov 14 Stephen Rothwell
2012-11-14 5:37 ` Andrew Morton
2012-11-14 5:53 ` Andrew Morton
2012-11-14 6:47 ` Ingo Molnar
2012-11-14 6:56 ` Andrew Morton
2012-11-14 7:15 ` Stephen Rothwell
2012-11-14 7:24 ` Andrew Morton
2012-11-14 7:39 ` Ingo Molnar
2012-11-14 8:13 ` Hugh Dickins
2012-11-14 17:05 ` Rik van Riel
2012-11-15 12:10 ` Mel Gorman
2012-11-14 17:19 ` Linus Torvalds
2012-11-14 6:55 ` Stephen Rothwell
2012-11-14 7:03 ` Stephen Rothwell
2012-11-14 19:41 ` linux-next: Tree for Nov 14 (gpu/drm/i915) Randy Dunlap
2012-11-14 20:17 ` Andrew Morton [this message]
2012-11-15 0:59 ` [PATCH 1/2] asm-generic: add __WARN() to bug.h Randy Dunlap
2012-11-15 1:28 ` David Rientjes
2012-11-15 0:59 ` [PATCH 2/2] mm: balloon_compaction.c needs asm-generic/bug.h Randy Dunlap
2012-11-15 1:29 ` David Rientjes
2012-11-15 1:29 ` Randy Dunlap
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=20121114121747.46ffe05f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).