public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: mingo@elte.hu, clameter@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix boundary checking in free_bootmem_core
Date: Wed, 12 Mar 2008 16:33:59 -0700	[thread overview]
Message-ID: <20080312163359.7fe0fd80.akpm@linux-foundation.org> (raw)
In-Reply-To: <86802c440803121621j3b9ec7e8nf7ae62b894eb85df@mail.gmail.com>

On Wed, 12 Mar 2008 16:21:22 -0700
"Yinghai Lu" <yhlu.kernel@gmail.com> wrote:

> On Tue, Mar 11, 2008 at 6:01 PM, Yinghai Lu <yhlu.kernel@gmail.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@gmail.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?

  reply	other threads:[~2008-03-12 23:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  1:01 [PATCH] mm: fix boundary checking in free_bootmem_core Yinghai Lu
2008-03-12 23:21 ` Yinghai Lu
2008-03-12 23:33   ` Andrew Morton [this message]
2008-03-13  1:11     ` Yinghai Lu
2008-03-13  1:22       ` Andrew Morton
2008-03-13 21:59         ` Andi Kleen
2008-03-13 22:22           ` Yinghai Lu
2008-03-14 11:58             ` Andi Kleen
2008-03-14 16:44               ` Yinghai Lu
2008-03-14 16:53                 ` Andi Kleen
2008-03-14 17:36                   ` Yinghai Lu
2008-03-21 19:44                     ` Andrew Morton
2008-03-21 20:00                       ` Ingo Molnar
2008-03-21 21:54                       ` Thomas Gleixner

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=20080312163359.7fe0fd80.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yhlu.kernel@gmail.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