datapath-windows: Incorrect assumption of the IRQL
authorSorin Vinturis <svinturis@cloudbasesolutions.com>
Mon, 6 Oct 2014 15:19:23 +0000 (15:19 +0000)
committerBen Pfaff <blp@nicira.com>
Mon, 6 Oct 2014 22:35:11 +0000 (15:35 -0700)
commit1ce4551c8c158e465734e26589d8444477cd5218
tree7e86952e3111ff35b5127de82ee4c4e9f01cafe8
parent52a524eb20462dd20d2e4e38d0fe97c07de040a7
datapath-windows: Incorrect assumption of the IRQL

Acquiring a spin lock raises the IRQL to DISPATCH_LEVEL. But
in many places of the code, while holding a spin lock, there
are useless checks for the current IRQL against DISPATCH_LEVEL.
Also, the dispatch flag is not correctly set when calling
NdisAcquireRWLockXXX() functions, which causes an extra check
of the current IRQL.

Signed-off-by: Sorin Vinturis <svinturis@cloudbasesolutions.com>
Reported-by: Sorin Vinturis <svinturis@cloudbasesolutions.com>
Reported-at: https://github.com/openvswitch/ovs-issues/issues/47
Acked-by: Nithin Raju <nithin@vmware.com>
Acked-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com>
Acked-by: Eitan Eliahu <eliahue@vmware.com>
Signed-off-by: Ben Pfaff <blp@nicira.com>
datapath-windows/ovsext/Datapath.c
datapath-windows/ovsext/Flow.c
datapath-windows/ovsext/PacketIO.c