[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080312163359.7fe0fd80.akpm@linux-foundation.org>
Date: Wed, 12 Mar 2008 16:33:59 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Yinghai Lu" <yhlu.kernel@...il.com>
Cc: mingo@...e.hu, clameter@....com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: fix boundary checking in free_bootmem_core
On Wed, 12 Mar 2008 16:21:22 -0700
"Yinghai Lu" <yhlu.kernel@...il.com> wrote:
> On Tue, Mar 11, 2008 at 6:01 PM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
> > [PATCH] mm: fix boundary checking in free_bootmem_core
> >
> > so call it when numa is enabled, we don't know which node have that range.
> > and make it more robust.
> >
> > try to trim it to get valid sidx, and eidx.
> >
> > Signed-off-by: Yinghai Lu <yhlu.kernel@...il.com>
> >
>
> Ingo,
>
> this one need to be applied before
> [PATCH] x86_64: reserve dma32 early for gart
>
So perhaps we should merge
mm-fix-boundary-checking-in-free_bootmem_core.patch into 2.6.25?
<looks at it>
Sorry, but I find the changelog very hard to amke sense of. I presently
have:
So call it when numa is enabled, we don't know which node have that
range. and make it more robust.
Try to trim it to get valid sidx, and eidx.
Could you please expand on this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists