Series Reviewed-By: Wu Jiaxin <[email protected]> Best Regards! Jiaxin
> -----Original Message----- > From: edk2-devel [mailto:[email protected]] On Behalf Of > Fu Siyuan > Sent: Tuesday, July 12, 2016 9:50 AM > To: [email protected] > Subject: [edk2] [Patch 0/2] Fix bug in TCP which not sending out ACK > > Consider the situation as shown in below chart. The last ACK message > has acknowledged the Tcb->RcvWl2, and all the segments until > Tcb->RcvNxt have been received by TCP driver. The Tcb->RcvNxt is not > acknowledged due to the delayed ACK. In this case an incoming segment > (Seg->Seq, Seg->End) should not be accepted by TCP driver, and an immediate > ACK is required. > > Current TcpSeqAcceptable() thought it s an acceptable segment > incorrectly, it continues the TcpInput() process instead of sending > out an ACK and droping the segment immediately. > > Tcb->RcvWl2 Tcb->RcvNxt Tcb->RcvWl2 + Tcb->RcvWnd > Seg->Seq Seg->End | | > | | | | | > > ---+-----+---------------+-------------+--------------------------+----------- > <income segment> <----Acceptable Range--- --> > > Fu Siyuan (2): > NetworkPkg: Fix bug in TCP which not sending out ACK in certain > circumstance. > MdeModulePkg: Fix bug in TCP which not sending out ACK in certain > circumstance. > > MdeModulePkg/Universal/Network/Tcp4Dxe/Tcp4Input.c | 2 +- > NetworkPkg/TcpDxe/TcpInput.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > -- > 2.7.4.windows.1 _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
