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

Nithin Raju nithin at vmware.com
Tue Nov 18 15:24:19 UTC 2014


On Nov 18, 2014, at 12:15 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.
> 
> Signed-off-by: Sorin Vinturis <svinturis at cloudbasesolutions.com>
> Reported-by: Sorin Vinturis <svinturis at cloudbasesolutions.com>
> Reported-at: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs-2Dissues_issues_53&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=pNHQcdr7B40b4h6Yb7FIedI1dnBsxdDuTLBYD3JqV80&m=vEsNeZnOUkZPbwbim_jaLF_M8X7XlDz7j7Cx6l9QqVY&s=9hmcwbIGTv6ar4IXXMTXnUSb-bvlM9T_s_RFHceIYek&e= 
> Acked-by: Eitan Eliahu <eliahue at vmware.com>
> ---

Acked-by: Nithin Raju <nithin at vmware.com>


More information about the dev mailing list