public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Mike Kravetz <mjkravetz@verizon.net>
Cc: Andrew Morton <akpm@osdl.org>, Arnd Bergmann <arnd@arndb.de>,
	Joel H Schopp <jschopp@us.ibm.com>,
	Andy Whitcroft <apw@shadowen.org>,
	lhms-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparsemem interaction with memory add bug fixes
Date: Wed, 12 Apr 2006 07:46:04 -0700	[thread overview]
Message-ID: <1144853164.31255.82.camel@localhost.localdomain> (raw)
In-Reply-To: <20060412023347.GA9343@w-mikek2.ibm.com>

On Tue, 2006-04-11 at 19:33 -0700, Mike Kravetz wrote:
> This patch fixes two bugs with the way sparsemem interacts with memory
> add.  They are:
> - memory leak if memmap for section already exists
> - calling alloc_bootmem_node() after boot
> These bugs were discovered and a first cut at the fixes were provided by
> Arnd Bergmann <arnd@arndb.de> and Joel Schopp <jschopp@us.ibm.com>.

At first glance, these seem fine to me.

Just out of curiosity.  Can these issues be revealed with current code,
or do they only show up with the cell changes?

-- Dave


  parent reply	other threads:[~2006-04-12 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12  2:33 [PATCH] sparsemem interaction with memory add bug fixes Mike Kravetz
2006-04-12  9:32 ` [Lhms-devel] " jschopp
2006-04-12 13:22 ` Andy Whitcroft
2006-04-12 13:43   ` jschopp
2006-04-12 14:46 ` Dave Hansen [this message]
2006-04-12 16:05   ` [Lhms-devel] " Mike Kravetz
  -- strict thread matches above, loose matches on Subject: below --
2006-04-12 17:19 Mike Kravetz

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=1144853164.31255.82.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=arnd@arndb.de \
    --cc=jschopp@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjkravetz@verizon.net \
    /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