On Fri, Apr 04, 2014 at 01:43:00PM +0200, Rafael J. Wysocki wrote: > > We need to ensure the cpuidle data structure is not going away (e.g. > > cpuidle driver module removal) while another CPU looks at it though. > > The timing would have to be awfully weird for this to happen but still. > > Well, I'm not sure if that is a real concern. Only a couple of drivers try > to implement module unloading and I guess this isn't tested too much, so > perhaps we should just make it impossible to unload a cpuidle driver?
The 'easy' solution is to mandate the use of rcu_read_lock() around the dereference and make all cpuidle drivers put an rcu_barrier() in their module unload path. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
