[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150528112002.GE3644@twins.programming.kicks-ass.net>
Date: Thu, 28 May 2015 13:20:02 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: mingo@...nel.org, mathieu.desnoyers@...icios.com, oleg@...hat.com,
paulmck@...ux.vnet.ibm.com, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, andi@...stfloor.org,
rostedt@...dmis.org, tglx@...utronix.de, laijs@...fujitsu.com,
linux@...izon.com
Subject: Re: [PATCH v5 00/10] latched RB-trees and __module_address()
On Thu, May 28, 2015 at 11:37:17AM +0930, Rusty Russell wrote:
> That's rcu_read_lock_sched_held, not rcu_held_lock_sched_held().
>
> Also, your unlikely is weird and backwards.
>
> I changed it as below, and folded. It's in modules-next.
>
> I'm now going to do some *actual* testing, and I'll go all Torvalds on
> you if this spews warnings...
Fair enough, I did see the build robot fail on this. How come those only
showed up now? This patch has been in your git tree for a long time; you
picked up the rcu validation patches before the other ones.
--
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/
Powered by blists - more mailing lists