From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [Patch] rcupdate: remove dead code
Date: Sun, 30 Jan 2011 23:59:00 -0800 [thread overview]
Message-ID: <20110131075900.GC2145@linux.vnet.ibm.com> (raw)
In-Reply-To: <1296382988-16564-1-git-send-email-amwang@redhat.com>
On Sun, Jan 30, 2011 at 06:23:08PM +0800, Amerigo Wang wrote:
> DEBUG_OBJECTS_RCU_HEAD depends on PREEMPT, so #ifndef CONFIG_PREEMPT
> is totally useless in kernel/rcupdate.c.
Queued, thank you, Amerigo!
I added a patch on top of this commenting why DEBUG_OBJECTS_RCU_HEAD
is disallowed if !PREEMPT, FYI.
Thanx, Paul
> Signed-off-by: WANG Cong <amwang@redhat.com>
> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
>
> ---
> diff --git a/kernel/rcupdate.c b/kernel/rcupdate.c
> index a23a57a..afd21d1 100644
> --- a/kernel/rcupdate.c
> +++ b/kernel/rcupdate.c
> @@ -215,10 +215,6 @@ static int rcuhead_fixup_free(void *addr, enum debug_obj_state state)
> * If we detect that we are nested in a RCU read-side critical
> * section, we should simply fail, otherwise we would deadlock.
> */
> -#ifndef CONFIG_PREEMPT
> - WARN_ON(1);
> - return 0;
> -#else
> if (rcu_preempt_depth() != 0 || preempt_count() != 0 ||
> irqs_disabled()) {
> WARN_ON(1);
> @@ -229,7 +225,6 @@ static int rcuhead_fixup_free(void *addr, enum debug_obj_state state)
> rcu_barrier_bh();
> debug_object_free(head, &rcuhead_debug_descr);
> return 1;
> -#endif
> default:
> return 0;
> }
prev parent reply other threads:[~2011-01-31 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 10:23 [Patch] rcupdate: remove dead code Amerigo Wang
2011-01-30 10:25 ` Cong Wang
2011-01-31 7:59 ` Paul E. McKenney
2011-01-31 7:59 ` 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=20110131075900.GC2145@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=amwang@redhat.com \
--cc=dipankar@in.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 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.