From: Johannes Weiner <hannes@saeurebad.de>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix spurious BUG_ON() in mark_bootmem()
Date: Thu, 10 Jul 2008 00:43:42 +0200 [thread overview]
Message-ID: <87fxqillup.fsf@saeurebad.de> (raw)
In-Reply-To: <1215637772.18157.6.camel@lts-notebook> (Lee Schermerhorn's message of "Wed, 09 Jul 2008 17:09:32 -0400")
Hi Lee,
Lee Schermerhorn <Lee.Schermerhorn@hp.com> writes:
> Against: 2.6.26-rc8-mm1
>
> Fixes problem introduced by patches:
>
> bootmem-factor-out-the-marking-of-a-pfn-range.patch
> bootmem-replace-node_boot_start-in-struct-bootmem_data.patch
>
> HP ia64 NUMA platform fails to boot 26-rc8-mm1, hitting BUG_ON()
> in mm/bootmem.c:mark_bootmem().
>
> After linking all bootmem chunks, the 'bdata_list' on HP ia64 numa
> platforms looks something like this:
>
> node 4: 0x0-0x8000
> node 0: 0x1c008000-0x1c07ec00
> node 1: 0x1c800000-0x1c87f000
> node 2: 0x1d000000-0x1d07f000
> node 3: 0x1d800000-0x1d87f000
>
> [Node 4 is a pseudo-node generated by the platform firmware to
> contain a configurable amount of zero-based, hardware interleaved
> memory. 0x8000 pages or 512M is the minimum that can be configured.]
>
> First call to mark_bootmem() [from free_bootmem()] called with:
>
> start-end: 0x1c008063-0x1c008262, reserve: 0, flags: 0
>
> I.e, NOT in the first chunk of the list.
>
> However, the "if (pos < bdata->node_min_pfn)" in the loop fails
> to test the start address of the argument range [in 'pos'] against
> the end of the chunk. So, it treats the range as being in the node
> 4 chunk. Second time thru' the loop, pos == 0x8000 is <
> bdata->node_min_pfn and pos != start, so we trip the BUG_ON().
>
> This patch enhances the if condition to skip chunks that do not
> overlap the argument range, allowing 26-rc8-mm1 to boot on this
> platform.
>
> Signed-off-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
>
> mm/bootmem.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.26-rc8-mm1/mm/bootmem.c
> ===================================================================
> --- linux-2.6.26-rc8-mm1.orig/mm/bootmem.c 2008-07-09 16:11:23.000000000 -0400
> +++ linux-2.6.26-rc8-mm1/mm/bootmem.c 2008-07-09 16:13:46.000000000 -0400
> @@ -299,7 +299,8 @@ static int __init mark_bootmem(unsigned
> int err;
> unsigned long max;
>
> - if (pos < bdata->node_min_pfn) {
> + if (pos < bdata->node_min_pfn ||
> + pos >= bdata->node_low_pfn) {
> BUG_ON(pos != start);
> continue;
> }
Ah, yeah, this was obviously wrong. Thanks for the fix!
Acked-by: Johannes Weiner <hannes@saeurebad.de>
Nice to know that it boots otherwise on such a setup :)
Hannes
prev parent reply other threads:[~2008-07-09 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 21:09 [PATCH] Fix spurious BUG_ON() in mark_bootmem() Lee Schermerhorn
2008-07-09 22:43 ` Johannes Weiner [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=87fxqillup.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.