public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, shijie8@gmail.com, tj@kernel.org,
	stable@kernel.org
Subject: Re: Patch "percpu: fix a memory leak in pcpu_extend_area_map()" has been added to the 2.6.35-stable tree
Date: Fri, 17 Sep 2010 01:37:23 +0200	[thread overview]
Message-ID: <201009170137.29317.s.L-H@gmx.de> (raw)
In-Reply-To: <20100916224721.GA14256@suse.de>

Hi

On Friday 17 September 2010, Greg KH wrote:
> On Thu, Sep 16, 2010 at 11:39:02PM +0200, Stefan Lippers-Hollmann wrote:
[...]
> > On Thursday 16 September 2010, gregkh@suse.de wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >     percpu: fix a memory leak in pcpu_extend_area_map()
> > > to the 2.6.35-stable tree which can be found at:
> > >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > [...]
> > > From a002d148426f40bc2b7dc066982eb177cdebeaaa Mon Sep 17 00:00:00 2001
> > > From: Huang Shijie <shijie8@gmail.com>
> > > Date: Sun, 8 Aug 2010 14:39:07 +0200
> > > Subject: percpu: fix a memory leak in pcpu_extend_area_map()
> > > 
> > > From: Huang Shijie <shijie8@gmail.com>
> > > 
> > > commit a002d148426f40bc2b7dc066982eb177cdebeaaa upstream.
> > > 
> > > The original code did not free the old map.  This patch fixes it.
> > > 
> > > tj: use @old as memcpy source instead of @chunk->map, and indentation
> > >     and description update
> > 
> > This patch, as part of the current -stable queue-2.6.35, breaks booting for
> > me on nforce4/ AMD64 X2. Unfortunately it fails even before the serial 
> > console is initialized and the only messages shown on screen are:
> > 
> > Decompressing Linux... Parsing ELF... done.
> > Booting kernel.
[...]
> > > --- a/mm/percpu.c
> > > +++ b/mm/percpu.c
> > > @@ -390,7 +390,9 @@ static int pcpu_extend_area_map(struct p
> > >  		goto out_unlock;
> > >  
> > >  	old_size = chunk->map_alloc * sizeof(chunk->map[0]);
> > > -	memcpy(new, chunk->map, old_size);
> > > +	old = chunk->map;
> > > +
> > > +	memcpy(new, old, old_size);
> > >  
> > >  	/*
> > >  	 * map_alloc < PCPU_DFL_MAP_ALLOC indicates that the chunk is
> > 
> > Reverting just this patch from the current queue-2.6.35 fixes the issue for
> > me; gzipped kernel config (amd64) attached.
> 
> Does Linus's tree also cause the same problems for you?

Current linux-2.6 HEAD (v2.6.36-rc4-134-g03a7ab0) boots and works fine with
a config very closely derived from the previous one.

Regards
	Stefan Lippers-Hollmann

  reply	other threads:[~2010-09-16 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12845915543097@site>
2010-09-16 21:39 ` Patch "percpu: fix a memory leak in pcpu_extend_area_map()" has been added to the 2.6.35-stable tree Stefan Lippers-Hollmann
2010-09-16 22:47   ` Greg KH
2010-09-16 23:37     ` Stefan Lippers-Hollmann [this message]
2010-09-17  2:43   ` Huang Shijie
2010-09-17 12:25     ` Stefan Lippers-Hollmann

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=201009170137.29317.s.L-H@gmx.de \
    --to=s.l-h@gmx.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shijie8@gmail.com \
    --cc=stable@kernel.org \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox