Acked-by: Anand Kumar <[email protected]> Thanks, Anand Kumar
On 3/8/19, 1:23 PM, "[email protected] on behalf of Sairam Venugopal via dev" <[email protected] on behalf of [email protected]> wrote: 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 <[email protected]> --- datapath-windows/ovsext/PacketIO.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/datapath-windows/ovsext/PacketIO.c b/datapath-windows/ovsext/PacketIO.c index 38e3e5f..57c583c 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; } -- 2.9.0.windows.1 _______________________________________________ dev mailing list [email protected] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.openvswitch.org%2Fmailman%2Flistinfo%2Fovs-dev&data=02%7C01%7Ckumaranand%40vmware.com%7Cf88cb293def34509deba08d6a40c3a25%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C636876769821233618&sdata=zY5NZ0d2F9esM76HXvWahDOOFLSQ%2FFBUqioPBJ8Tdqo%3D&reserved=0 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
