From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, stable <stable@kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Eric Dumazet <dada1@cosmosbay.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] modules fix incorrect percpu usage
Date: Tue, 30 Mar 2010 09:50:47 -0400 [thread overview]
Message-ID: <20100330135047.GB20673@Krystal> (raw)
In-Reply-To: <1269955201.19685.5867.camel@gandalf.stny.rr.com>
* Steven Rostedt (rostedt@goodmis.org) wrote:
> On Mon, 2010-03-29 at 23:36 -0400, Mathieu Desnoyers wrote:
> > * Mathieu Desnoyers (mathieu.desnoyers@efficios.com) wrote:
> > > Should use per_cpu_ptr() to obfuscate the per cpu pointers (RELOC_HIDE is needed
> > > for per cpu pointers).
> > >
> > > Introduced by commit:
> > >
> > > module.c: commit 6b588c18f8dacfa6d7957c33c5ff832096e752d3
> > >
> > > This patch should be queued for the stable branch, for kernels 2.6.29.x to
> > > 2.6.33.x.
> > > (tested on 2.6.33.1 x86_64)
> >
> > It's actually needed for mainline too (2.6.34-rc2).
>
> Then all you need to do is submit it for mainline with a
> "Cc: stable@kernel.org" as you did below. It will then automatically be
> added to the stable queue when Linus pulls it.
OK, thanks for the info.
Mathieu
>
> -- Steve
>
> >
> > Thanks,
> >
> > Mathieu
> >
> > >
> > > Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > > CC: Randy Dunlap <randy.dunlap@oracle.com>
> > > CC: Eric Dumazet <dada1@cosmosbay.com>
> > > CC: Rusty Russell <rusty@rustcorp.com.au>
> > > CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > CC: Tejun Heo <tj@kernel.org>
> > > CC: Ingo Molnar <mingo@elte.hu>
> > > CC: Andrew Morton <akpm@linux-foundation.org>
> > > CC: Linus Torvalds <torvalds@linux-foundation.org>
> > > CC: Greg Kroah-Hartman <gregkh@suse.de>
> > > CC: Steven Rostedt <rostedt@goodmis.org>
> > > CC: stable <stable@kernel.org>
> > > ---
> > > kernel/module.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > >
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-03-30 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 3:32 [PATCH -stable] modules fix incorrect percpu usage Mathieu Desnoyers
2010-03-30 3:36 ` [PATCH] " Mathieu Desnoyers
2010-03-30 13:20 ` Steven Rostedt
2010-03-30 13:50 ` Mathieu Desnoyers [this message]
2010-04-19 18:28 ` [stable] " Greg KH
2010-04-20 14:34 ` Mathieu Desnoyers
2010-04-21 10:51 ` Tejun Heo
2010-04-21 22:39 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-03-30 13:52 Mathieu Desnoyers
2010-03-30 19:53 ` Andrew Morton
2010-03-30 20:24 ` Mathieu Desnoyers
2010-03-31 2:03 ` Steven Rostedt
2010-03-31 2:15 ` Tejun Heo
2010-03-31 1:49 ` Tejun Heo
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=20100330135047.GB20673@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=stable@kernel.org \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox