linux-kernel - Re: [RFC][PATCH] lockdep/rcu: Find where rcu/pi/rq lock problems occur

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 15 Aug 2011 12:47:15 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC][PATCH] lockdep/rcu: Find where rcu/pi/rq lock problems
 occur

On Mon, 2011-08-15 at 12:43 -0400, Steven Rostedt wrote:
> +
> +#else /* CONFIG_PREEMPT_RCU */
> +static inline void lockdep_rcu_irq(int on) { }

I need to also add:

static inline void test_lock_type(...) { } 

here too. Fixed, for the next release.

-- Steve

> +#endif
> + 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/