Lines Matching full:ack
153 "Delay ACK to try and piggyback it onto a data packet");
208 "Follow RFC793 criteria for validating SEG.ACK");
252 * receiving a duplicate ACK with a SACK block, and also
400 * If a SYN or SYN/ACK was lost and retransmitted, we have to
405 tp->snd_cwnd = maxseg; /* SYN(-ACK) lost */
433 * Allow ECN reaction on ACK to CWR, if
500 * Indicate whether this ack should be delayed. We can delay the ack if
502 * - There is no delayed ack timer in progress.
503 * - Our last ack wasn't a 0-sized window. We never want to delay
504 * the ack that opens up a 0-sized window.
559 * tcp_do_segment processes the ACK and text of the segment for
1065 * the flag is only ACK. A successful lookup creates a new
1089 * No syncache entry, or ACK was not for our
1090 * SYN/ACK. Do our protection against double
1091 * ACK. If peer sent us 2 ACKs, then for the
1095 * don't want to sent RST for the second ACK,
1098 * the ACK is stray indeed, rstreason would
1119 * retransmit the ACK for another
1165 * Our (SYN|ACK) response was rejected.
1188 * (SYN|ACK) is bogus on a listen socket.
1193 "SYN|ACK invalid, segment rejected\n",
1388 * the segment silently, or send a challenge ACK. However, we try
1569 * If a segment with the ACK-bit set arrives in the SYN-SENT state
1570 * check SEQ.ACK first.
1649 * Process options only when we get SYN/ACK back. The SYN case
1652 * or <SYN,ACK>) segment itself is never scaled.
1711 * If timestamps were negotiated during SYN/ACK and a
1735 * If timestamps were not negotiated during SYN/ACK and a
1753 * candidate. If the length is zero and the ack moved
1757 * is non-zero and the ack didn't move, we're the
1760 * the socket buffer and note that we need a delayed ack.
1775 * If last ACK falls within this segment's sequence numbers,
1793 * This is a pure ack for outstanding data.
1812 * during the SYN+ACK phase, ignore
1878 * a sufficiently large ACK.
1893 * or we need to send an ACK.
1983 * if seg contains an ACK, but not for our SYN/ACK, send a RST.
2002 * a subset of the original data), a valid ACK, a
2022 * if seg contains a RST with valid ACK (SEQ.ACK has already
2024 * if seg contains a RST without an ACK, drop the seg.
2028 * if seg contains ack then advance tp->snd_una
2077 * If there's data, delay ACK; if there's also a FIN
2089 * Received <SYN,ACK> in SYN_SENT[*] state.
2141 * our data will be ACK'd; if so, enter normal data segment
2142 * processing in the middle of step 5, ack processing.
2164 * drop leading data (and SYN); if nothing left, just ack.
2171 * - If RST is in window, we send challenge ACK.
2217 * Send challenge ACK for any SYN in synchronized state.
2303 * Send an ACK to resynchronize and drop any data.
2304 * But keep on processing for RST or ACK.
2321 * ACK now, as the next in-sequence segment
2362 * (and PUSH and FIN); if nothing left, just ACK.
2373 * remember to ack. Otherwise, drop segment
2374 * and ack.
2389 * If last ACK falls within this segment's sequence numbers,
2398 * Last.ACK.Sent <= SEG.SEQ + SEG.Len
2400 * Last.ACK.Sent < SEG.SEQ + SEG.Len,
2404 * RTT correctly when RCV.NXT == Last.ACK.Sent.
2415 * If the ACK bit is off: if in SYN-RECEIVED state or SENDSYN
2435 * Ack processing.
2438 /* Checking SEG.ACK against ISS is definitely redundant. */
2475 * In SYN_RECEIVED state, the ack ACKs our SYN, so enter
2477 * The ACK was checked above.
2523 * snd_cwnd reduction that occurs when a TFO SYN|ACK
2531 * Account for the ACK of our SYN prior to
2532 * regular ACK processing below, except for
2538 * If segment contains data or ACK, will call tcp_reass()
2550 * In ESTABLISHED state: drop duplicate ACKs; ACK out of range
2551 * ACKs. If the ack is in the range
2554 * data from the retransmission queue. If this ACK reflects
2576 * from the last ack with SACK doesn't get used.
2606 * duplicate ack (ie, window info didn't
2608 * the ack is the biggest we've
2726 /* Congestion signal before ack. */
2792 * ACK by increasing snd_cwnd by one
2820 * or we need to send an ACK.
2849 * This ack is advancing the left edge, reset the
2854 * If this ack also has new SACK info, increment the
2919 * If we reach this point, ACK is not a duplicate,
2925 * SYN has been ACK'd (so connection is now fully
2927 * increment snd_una for ACK of SYN, and check if
2960 * If we just performed our first retransmit, and the ACK
2984 * during the SYN+ACK phase, ignore
3006 * large ACK.
3028 * If no data (only SYN) was ACK'd,
3029 * skip rest of ACK processing.
3107 * the ESTABLISHED state if the ACK acknowledges our FIN
3121 * and/or to be acked, as well as for the ack of our FIN.
3139 * Don't look at window if no ACK: TAC's send garbage on first SYN.
3246 * Set DELACK for segments received in order, but ack
3370 * If FIN is received ACK the FIN and let the user know
3379 * (ie NEEDSYN flag on) then delay ACK,
3382 * more input can be expected, send ACK now.
3440 * Generate an ACK dropping incoming segment if it occupies
3441 * sequence space, where the ACK reflects our state.
3447 * In the SYN-RECEIVED state, don't send an ACK unless the
3448 * segment we received passes the SYN-RECEIVED ACK test.
3450 * "LAND" DoS attack, and also prevents an ACK storm
3488 * Issue RST and make ACK acceptable to originator of segment.
3768 * We received an ack for a packet that wasn't retransmitted;
3795 * segment, or an ICMP need fragmentation datagram. Outgoing SYN/ACK MSS
4096 * Compute the amount of data that this ACK is indicating
4131 * - A partial ack without SACK block beneath snd_recover
4136 * - Prevent ACK splitting attacks, by being conservative
4151 * Send snd_cnt new data into the network in response to this ack.
4169 * On a partial ack arrives, force the retransmission of the