summaryrefslogtreecommitdiff
path: root/datapath-windows
diff options
context:
space:
mode:
authorSairam Venugopal <vsairam@vmware.com>2019-03-08 13:22:33 -0800
committerAlin Gabriel Serdean <aserdean@ovn.org>2019-03-13 13:18:22 +0200
commit9c60fd48790afac901696c07b2befef3d2ea6301 (patch)
tree081bedb1f1bb68f202eca72720526839e430b7c3 /datapath-windows
parenta47e2db209e4da594ea35202f59d14371c2078a7 (diff)
downloadopenvswitch-9c60fd48790afac901696c07b2befef3d2ea6301.tar.gz
datapath-windows: Fix nbl cleanup when memory allocation fails
StartNblIngressError should be called only when an NBL hasn't been modified. In this case the nbl context was initialized. Rely on existing packet completion mechanism to cleanup the NBL. Found while testing with DriverVerifier with limited memory setting enabled. Signed-off-by: Sairam Venugopal <vsairam@vmware.com> Acked-by: Anand Kumar <kumaranand@vmware.com> Signed-off-by: Alin Gabriel Serdean <aserdean@ovn.org>
Diffstat (limited to 'datapath-windows')
-rw-r--r--datapath-windows/ovsext/PacketIO.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/datapath-windows/ovsext/PacketIO.c b/datapath-windows/ovsext/PacketIO.c
index 38e3e5f36..57c583ccf 100644
--- a/datapath-windows/ovsext/PacketIO.c
+++ b/datapath-windows/ovsext/PacketIO.c
@@ -283,9 +283,8 @@ OvsStartNBLIngress(POVS_SWITCH_CONTEXT switchContext,
RtlInitUnicodeString(&filterReason,
L"Cannot allocate NBLs with single NB.");
- OvsStartNBLIngressError(switchContext, curNbl,
- sendCompleteFlags, &filterReason,
- NDIS_STATUS_RESOURCES);
+ OvsAddPktCompletionList(&completionList, TRUE, sourcePort,
+ curNbl, 0, &filterReason);
continue;
}