[ovs-dev] [PATCH v4] datapath-windows: Avoid BSOD when switch context is NULL

Nithin Raju nithin at vmware.com
Tue Nov 18 07:12:20 UTC 2014


On Nov 17, 2014, at 9:39 AM, Sorin Vinturis <svinturis at cloudbasesolutions.com> wrote:

> I came around a BSOD that happened when trying to access pidHashLock
> from the gOvsSwitchContext, which was NULL. The stop happened in
> OvsAcquirePidHashLock function.
> 
> To reproduce this BSOD, make sure the extension is enabled and running,
> disable it and, after that, execute 'ovs-dpctl.exe show'. The BSOD is
> triggered afterwards.

Sorin,
I believe I have reviewed the v3 of this patch, and I have some comments. Pls. have a look.

thanks,
-- Nithin


More information about the dev mailing list