Hi John, So yeah, I just didn't try hard enough it seems; how about this?
Also, I think we should double check that everything passed to tk_setup_internals(.clock) is either static storage or RCU-sched freed, because with the whole latch thing one CPUs (fast) access might still be in progress while the other is freeing the clock struct. Not sure what the lifetime rules of struct clocksource are here. -- 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/
