From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] rcu: add missing __cpuinit annotation in rcutorture code
Date: Tue, 27 Dec 2011 09:29:51 -0800 [thread overview]
Message-ID: <20111227172951.GC2889@linux.vnet.ibm.com> (raw)
In-Reply-To: <1324994666-4080-1-git-send-email-heiko.carstens@de.ibm.com>
On Tue, Dec 27, 2011 at 03:04:26PM +0100, Heiko Carstens wrote:
> "rcu: Add rcutorture CPU-hotplug capability" adds cpu hotplug operations
> to the rcutorture code but produces a false positive warning about section
> mismatches:
>
> WARNING: vmlinux.o(.text+0x1e420c): Section mismatch in reference from the
> function rcu_torture_onoff() to the function .cpuinit.text:cpu_up()
> The function rcu_torture_onoff() references
> the function __cpuinit cpu_up().
> This is often because rcu_torture_onoff lacks a __cpuinit
> annotation or the annotation of cpu_up is wrong.
>
> Just add a __cpuinit annotation so the warning goes away.
>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Thank you -- queued on my local -rcu tree.
Thanx, Paul
> ---
> kernel/rcutorture.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/rcutorture.c b/kernel/rcutorture.c
> index e29edc3..a58ac28 100644
> --- a/kernel/rcutorture.c
> +++ b/kernel/rcutorture.c
> @@ -1399,7 +1399,7 @@ rcu_torture_shutdown(void *arg)
> * Execute random CPU-hotplug operations at the interval specified
> * by the onoff_interval.
> */
> -static int
> +static int __cpuinit
> rcu_torture_onoff(void *arg)
> {
> int cpu;
> @@ -1447,7 +1447,7 @@ rcu_torture_onoff(void *arg)
> return 0;
> }
>
> -static int
> +static int __cpuinit
> rcu_torture_onoff_init(void)
> {
> if (onoff_interval <= 0)
> --
> 1.7.7.3
>
prev parent reply other threads:[~2011-12-27 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 14:04 Heiko Carstens
2011-12-27 17:29 ` Paul E. McKenney [this message]
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=20111227172951.GC2889@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.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
Powered by JetHome