From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: paulmck@linux.vnet.ibm.com, rgb@redhat.com, eparis@redhat.com
Subject: audit: rcu_read_lock() used illegally while idle
Date: Wed, 3 Dec 2014 13:19:22 -0500 [thread overview]
Message-ID: <20141203181922.GA26916@redhat.com> (raw)
I'm not sure why this only just started complaining, because this code
hasn't changed in years, but I don't recall seeing this before.
This gets spewed during bootup since I put 3.18-rc7 on my firewall.
Previously it was running rc4 where I didn't see this.
Did something in RCU change recently ?
===============================
[ INFO: suspicious RCU usage. ]
3.18.0-rc7+ #93 Not tainted
-------------------------------
include/linux/rcupdate.h:883 rcu_read_lock() used illegally while idle!
other info that might help us debug this:
RCU used illegally from idle CPU!
rcu_scheduler_active = 1, debug_locks = 0
RCU used illegally from extended quiescent state!
1 lock held by systemd-sysctl/557:
#0: (rcu_read_lock){......}, at: [<ffffffff890f1320>] audit_filter_type+0x0/0x240
stack backtrace:
CPU: 0 PID: 557 Comm: systemd-sysctl Not tainted 3.18.0-rc7+ #93
0000000000000000 0000000063c50efc ffff88021f51fd28 ffffffff895abec3
0000000000000000 ffff880234758000 ffff88021f51fd58 ffffffff890a5280
ffff880221d9c548 00007fd651f320d0 0000000000000514 00000000ffff9012
Call Trace:
[<ffffffff895abec3>] dump_stack+0x4e/0x68
[<ffffffff890a5280>] lockdep_rcu_suspicious+0xf0/0x110
[<ffffffff890f150e>] audit_filter_type+0x1ee/0x240
[<ffffffff890f1320>] ? audit_filter_user+0x340/0x340
[<ffffffff890ecd39>] audit_log_start+0x49/0x4a0
[<ffffffff8908f4f5>] ? local_clock+0x25/0x30
[<ffffffff890a397f>] ? lock_release_holdtime.part.30+0xf/0x190
[<ffffffff890f1973>] audit_log_exit+0x53/0xcf0
[<ffffffff8908f4f5>] ? local_clock+0x25/0x30
[<ffffffff890a397f>] ? lock_release_holdtime.part.30+0xf/0x190
[<ffffffff895b4f0c>] ? sysret_signal+0x5/0x43
[<ffffffff890f4a65>] __audit_syscall_exit+0x245/0x2a0
[<ffffffff895b4f61>] sysret_audit+0x17/0x21
next reply other threads:[~2014-12-03 18:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 18:19 Dave Jones [this message]
2014-12-03 19:29 ` audit: rcu_read_lock() used illegally while idle Paul E. McKenney
2014-12-03 20:06 ` Andy Lutomirski
2014-12-03 20:19 ` Dave Jones
2014-12-03 20:38 ` Andy Lutomirski
2014-12-03 22:08 ` Frederic Weisbecker
2014-12-03 22:12 ` Andy Lutomirski
2014-12-03 23:49 ` Frederic Weisbecker
2014-12-03 23:18 ` [PATCH] context_tracking: Restore previous state in schedule_user Andy Lutomirski
2014-12-03 23:26 ` Andy Lutomirski
2014-12-03 23:31 ` Dave Jones
2014-12-03 23:58 ` Frederic Weisbecker
2014-12-04 0:04 ` Andy Lutomirski
2014-12-04 0:30 ` Dave Jones
2014-12-04 0:38 ` Andy Lutomirski
2014-12-04 1:13 ` Frederic Weisbecker
2014-12-03 23:37 ` [PATCH v2] " Andy Lutomirski
2014-12-03 23:50 ` Paul E. McKenney
2014-12-04 0:01 ` Frederic Weisbecker
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=20141203181922.GA26916@redhat.com \
--to=davej@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rgb@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox