From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.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>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Steven Rostedt <rostedt@goodmis.org>, stable <stable@kernel.org>
Subject: Re: [PATCH] modules fix incorrect percpu usage
Date: Tue, 30 Mar 2010 12:53:04 -0700 [thread overview]
Message-ID: <20100330125304.53f079db.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100330135208.GC20673@Krystal>
On Tue, 30 Mar 2010 09:52:08 -0400
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
>
> It applies to mainline as of 2.6.34-rc2. This patch should be queued for the
> stable branch, for kernels 2.6.29.x to 2.6.33.x.
> (based on 2.6.33.1, also applies to 2.6.34-rc2 -tip)
Why do you beleive this should be backported to -stable? What are the
user-visible effects of this change?
next prev parent reply other threads:[~2010-03-30 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 13:52 [PATCH] modules fix incorrect percpu usage Mathieu Desnoyers
2010-03-30 19:53 ` Andrew Morton [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2010-03-30 3:32 [PATCH -stable] " Mathieu Desnoyers
2010-03-30 3:36 ` [PATCH] " Mathieu Desnoyers
2010-03-30 13:20 ` Steven Rostedt
2010-03-30 13:50 ` 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=20100330125304.53f079db.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dada1@cosmosbay.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=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 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.