From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>,
Linux PPC dev <linuxppc-dev@ozlabs.org>,
"mpe >> Michael Ellerman" <mpe@ellerman.id.au>
Subject: Re: suspicious RCU usage clockevents_lock, tick_broadcast_lock, hrtimer_bases.lock
Date: Fri, 13 Feb 2015 10:57:19 +0530 [thread overview]
Message-ID: <54DD8B37.2040903@linux.vnet.ibm.com> (raw)
In-Reply-To: <54DD4BF6.1070503@au1.ibm.com>
On 02/13/2015 06:27 AM, Sam Bobroff wrote:
> Hello,
>
> I'm receiving this while booting a vanilla 3.19 kernel on a Power 8 machine:
Does the below patch fix the issue ?
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
[PATCH] tick/hrtimer-broadcast: Fix a suspicious RCU usage in the tick broadcast path
---
kernel/time/tick-broadcast-hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/tick-broadcast-hrtimer.c b/kernel/time/tick-broadcast-hrtimer.c
index eb682d5..57b8e32 100644
--- a/kernel/time/tick-broadcast-hrtimer.c
+++ b/kernel/time/tick-broadcast-hrtimer.c
@@ -62,7 +62,7 @@ static int bc_set_next(ktime_t expires, struct clock_event_device *bc)
* HRTIMER_RESTART.
*/
if (hrtimer_try_to_cancel(&bctimer) >= 0) {
- hrtimer_start(&bctimer, expires, HRTIMER_MODE_ABS_PINNED);
+ RCU_NONIDLE(hrtimer_start(&bctimer, expires, HRTIMER_MODE_ABS_PINNED));
/* Bind the "device" to the cpu */
bc->bound_on = smp_processor_id();
} else if (bc->bound_on == smp_processor_id()) {
--
Regards
Preeti U Murthy
>
> [ 2.522179] device-mapper: uevent: version 1.0.3
> [ 2.522741] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28)
> initialised: dm-devel@redhat.com
> [ 2.543590]
> [ 2.543630] ===============================
> [ 2.543709] [ INFO: suspicious RCU usage. ]
> [ 2.543758] 3.19.0samb #2 Not tainted
> [ 2.543802] -------------------------------
> [ 2.543847] include/trace/events/timer.h:186 suspicious
> rcu_dereference_check() usage!
> [ 2.543940]
> [ 2.543940] other info that might help us debug this:
> [ 2.543940]
> [ 2.544035]
> [ 2.544035] RCU used illegally from idle CPU!
> [ 2.544035] rcu_scheduler_active = 1, debug_locks = 0
> [ 2.544154] RCU used illegally from extended quiescent state!
> [ 2.544234] 3 locks held by swapper/1/0:
> [ 2.544284] #0: (clockevents_lock){-.....}, at:
> [<c0000000001a45cc>] .clockevents_notify+0x5c/0x320
> [ 2.544464] #1: (tick_broadcast_lock){-.-...}, at:
> [<c0000000001a7ac4>] .tick_broadcast_oneshot_control+0xe4/0x530
> [ 2.544654] #2: (hrtimer_bases.lock#2){-.-...}, at:
> [<c000000000192694>] .__hrtimer_start_range_ns+0x124/0x6e0
> [ 2.544843]
> [ 2.544843] stack backtrace:
> [ 2.544904] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.19.0samb #2
> [ 2.544986] Call Trace:
> [ 2.545023] [c000000fdf6f7770] [c000000000faf118]
> .dump_stack+0x98/0xd4 (unreliable)
> [ 2.545124] [c000000fdf6f77f0] [c000000000152b78]
> .lockdep_rcu_suspicious+0x138/0x180
> [ 2.545225] [c000000fdf6f7880] [c000000000191374]
> .enqueue_hrtimer+0x1c4/0x300
> [ 2.545325] [c000000fdf6f7910] [c00000000019276c]
> .__hrtimer_start_range_ns+0x1fc/0x6e0
> [ 2.545425] [c000000fdf6f7a10] [c0000000001a8e90] .bc_set_next+0xc0/0xf0
> [ 2.545510] [c000000fdf6f7aa0] [c0000000001a51f0]
> .clockevents_program_event+0x100/0x1f0
> [ 2.545607] [c000000fdf6f7b40] [c0000000001a6bac]
> .tick_broadcast_set_event+0x6c/0x120
> [ 2.545705] [c000000fdf6f7bd0] [c0000000001a7c94]
> .tick_broadcast_oneshot_control+0x2b4/0x530
> [ 2.545802] [c000000fdf6f7ca0] [c0000000001a4818]
> .clockevents_notify+0x2a8/0x320
> [ 2.545898] [c000000fdf6f7d70] [c0000000001484f4]
> .cpu_startup_entry+0x404/0x730
> [ 2.545995] [c000000fdf6f7ec0] [c000000000044314]
> .start_secondary+0x3a4/0x460
> [ 2.546092] [c000000fdf6f7f90] [c000000000008bfc]
> start_secondary_prolog+0x10/0x14
> [ 2.546555] Registering IBM Power 842 compression driver
>
> Cheers,
> Sam.
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2015-02-13 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 0:57 suspicious RCU usage clockevents_lock, tick_broadcast_lock, hrtimer_bases.lock Sam Bobroff
2015-02-13 5:27 ` Preeti U Murthy [this message]
2015-02-13 7:22 ` Preeti U Murthy
2015-02-13 14:26 ` Paul E. McKenney
2015-02-16 3:19 ` Preeti U Murthy
2015-02-16 5:50 ` Paul E. McKenney
2015-02-16 6:06 ` Preeti U Murthy
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=54DD8B37.2040903@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sam.bobroff@au1.ibm.com \
/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.