> I think dls_devnet_stat_update doen't need the mac perimeter itself. > Instead it needs to increment the dd_ref of the dls_devnet_t to make > sure it can't disappear. That should synchronize > dls_devnet_stat_create/update/destroy functions. A related thing is that > the functions will have to drop i_dls_devnet_lock before calling kstat > functions so that the order is kstat internal lock (or perimeter) -> > i_dls_devnet_lock. I will try this and let you know, so that you can try > the stress test on it (unless you have already coded up a fix).
That'd be great -- I have not coded up a fix. Is this really the only case in which IP may make a downcall which requires entering the perimeter? -- meem
