On Wed, Oct 05, 2016 at 11:01:38AM -0700, Cong Wang wrote: > Does the attached patch make any sense now? Our pernet init doesn't > rely on act_base, so even we have some race, the worst case is after > we initialize the pernet netns for an action but its ops still not > visible, which seems fine (at least no crash).
I tried to reproduce the panic with this latest patch, but I am unable to do so. The one difference I notice between this patch, and the one I sent to the list, is that with yours it takes much longer before we get any output from the simultaneous launch of these containers. Presumably that's the extra latency added by allowing many extra modprobe calls to get spawned by request_module(). -K
