From: Steven Rostedt <rostedt@goodmis.org>
To: John Kacur <jkacur@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break
Date: Mon, 14 Nov 2011 15:57:40 -0500 [thread overview]
Message-ID: <1321304260.5011.12.camel@frodo> (raw)
In-Reply-To: <1321235083-21756-1-git-send-email-jkacur@redhat.com>
On Mon, 2011-11-14 at 02:44 +0100, John Kacur wrote:
> kernel/rcutorture.c:492: error: ‘synchronize_rcu_bh’ undeclared here (not in a function)
>
> In CONFIG_PREEMPT_RT_FULL
> doesn't cover function pointer assignment unless we remove the brackets.
John,
Please write better change logs. Do not assume that people are looking
at the patch while looking at the logs. I mostly read change logs as
"git log" which doesn't include the changes, and most other developers
do this too. The above sentence does not make any real sense.
Something like:
synchronize_rcu_bh() is not just called as a normal function, but can
also be referenced as a function pointer. When CONFIG_PREEMPT_RT_FULL is
enabled, synchronize_rcu_bh() is defined as synchronize_rcu(), but needs
to be defined without the parenthesis because the compiler will complain
when synchronize_rcu_bh is referenced as a function pointer and not a
function.
-- Steve
>
> Compile-tested.
>
> Signed-off-by: John Kacur <jkacur@redhat.com>
> ---
> include/linux/rcutree.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/rcutree.h b/include/linux/rcutree.h
> index 800b840..6e503a3 100644
> --- a/include/linux/rcutree.h
> +++ b/include/linux/rcutree.h
> @@ -60,7 +60,7 @@ static inline void exit_rcu(void)
> #ifndef CONFIG_PREEMPT_RT_FULL
> extern void synchronize_rcu_bh(void);
> #else
> -# define synchronize_rcu_bh() synchronize_rcu()
> +# define synchronize_rcu_bh synchronize_rcu
> #endif
> extern void synchronize_sched_expedited(void);
> extern void synchronize_rcu_expedited(void);
prev parent reply other threads:[~2011-11-14 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:44 [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break John Kacur
2011-11-14 1:44 ` [PATCH 2/2] Compile error with allmodconfig and CONFIG_PREEMPT_RT_FULL=y John Kacur
2011-11-14 16:51 ` Paul E. McKenney
2011-11-14 17:39 ` John Kacur
2011-11-14 17:57 ` Paul E. McKenney
2011-11-14 20:51 ` Steven Rostedt
2011-11-14 21:07 ` John Kacur
2011-11-15 5:22 ` Mike Galbraith
2011-11-15 12:23 ` Steven Rostedt
2011-11-15 13:27 ` Mike Galbraith
2011-11-15 13:45 ` Mike Galbraith
2011-11-16 14:21 ` Mike Galbraith
2012-04-13 5:34 ` SUSE question wrt RT locking primitives Mike Galbraith
2012-04-13 12:58 ` Steven Rostedt
2012-04-13 14:53 ` Mike Galbraith
2012-04-13 15:47 ` Thomas Gleixner
2011-11-14 16:50 ` [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break Paul E. McKenney
2011-11-14 20:57 ` Steven Rostedt [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=1321304260.5011.12.camel@frodo \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).