From: Tejun Heo <tj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Peter Palfrader <peter@palfrader.org>,
stable@kernel.org, Huang Shijie <shijie8@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [stable] breaks 2.6.32.21+
Date: Fri, 17 Sep 2010 15:47:35 +0200 [thread overview]
Message-ID: <4C937177.1090909@kernel.org> (raw)
In-Reply-To: <20100916231307.GB24617@kroah.com>
On 09/17/2010 01:13 AM, Greg KH wrote:
> Odd, someone just reported the same problem for .35-stable as well.
>
> Tejun, what's going on here?
Please drop it. The memory leak was introduced after 2.6.36-rc1. I
got confused which commit was in which kernel. I'll be more careful
with stable cc's. Sorry about that.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Peter Palfrader <peter@palfrader.org>,
stable@kernel.org, Huang Shijie <shijie8@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [stable] breaks 2.6.32.21+
Date: Fri, 17 Sep 2010 15:47:35 +0200 [thread overview]
Message-ID: <4C937177.1090909@kernel.org> (raw)
In-Reply-To: <20100916231307.GB24617@kroah.com>
On 09/17/2010 01:13 AM, Greg KH wrote:
> Odd, someone just reported the same problem for .35-stable as well.
>
> Tejun, what's going on here?
Please drop it. The memory leak was introduced after 2.6.36-rc1. I
got confused which commit was in which kernel. I'll be more careful
with stable cc's. Sorry about that.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-09-17 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 9:53 [PATCH] percpu : fix the memory leak Huang Shijie
2010-08-08 12:42 ` [PATCH] percpu: fix a memory leak in pcpu_extend_area_map() Tejun Heo
2010-08-08 12:42 ` Tejun Heo
2010-08-26 22:10 ` Andrew Morton
2010-08-26 22:10 ` Andrew Morton
2010-08-27 9:32 ` Tejun Heo
2010-08-27 9:32 ` Tejun Heo
2010-09-16 21:36 ` breaks 2.6.32.21+ (was: [PATCH] percpu: fix a memory leak in pcpu_extend_area_map()) Peter Palfrader
2010-09-16 21:36 ` Peter Palfrader
2010-09-16 23:13 ` [stable] " Greg KH
2010-09-16 23:13 ` Greg KH
2010-09-17 13:47 ` Tejun Heo [this message]
2010-09-17 13:47 ` [stable] breaks 2.6.32.21+ Tejun Heo
2010-09-17 16:36 ` Greg KH
2010-09-17 16:36 ` Greg KH
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=4C937177.1090909@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peter@palfrader.org \
--cc=shijie8@gmail.com \
--cc=stable@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.