From: Tejun Heo <tj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
stable <stable@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, Eric Dumazet <dada1@cosmosbay.com>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [stable] [PATCH 2.6.29.x - 2.6.31.1] module: fix __module_ref_addr()
Date: Tue, 30 Mar 2010 11:12:46 +0900 [thread overview]
Message-ID: <4BB15E1E.70504@kernel.org> (raw)
In-Reply-To: <20100329210722.GA14993@kroah.com>
Hello, Greg.
On 03/30/2010 06:07 AM, Greg KH wrote:
>> Yes. 2.6.34-rc does not have this issue anymore, but the patch is needed in
>> -stable.
>
> Why is this not in .34-rc2? Can you find the specific patch in Linus's
> tree that solves this and let stable@kernel.org know about it?
For 2.6.34, the following two patches should remove the problem.
They're not in mainline yet but should appear in linux-next soon and
after a few days, I'll push them to Linus.
http://thread.gmane.org/gmane.linux.kernel/958794/focus=959493
Thanks.
--
tejun
next prev parent reply other threads:[~2010-03-30 2:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 14:31 [PATCH 2.6.29.x - 2.6.31.1] module: fix __module_ref_addr() Mathieu Desnoyers
2010-03-29 19:21 ` Steven Rostedt
2010-03-29 20:09 ` Mathieu Desnoyers
2010-03-29 21:07 ` [stable] " Greg KH
2010-03-30 1:08 ` Steven Rostedt
2010-03-30 2:22 ` Mathieu Desnoyers
2010-04-19 18:26 ` Greg KH
2010-04-20 14:38 ` Mathieu Desnoyers
2010-03-30 2:12 ` Tejun Heo [this message]
2010-03-30 2:34 ` Tejun Heo
2010-03-30 3:04 ` Mathieu Desnoyers
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=4BB15E1E.70504@kernel.org \
--to=tj@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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.