On Thu, Jan 10, 2013 at 9:18 PM, Eric Dumazet <[email protected]> wrote: > From: Eric Dumazet <[email protected]> > > On Thu, 2013-01-10 at 18:01 -0800, Eric Dumazet wrote: > >> Hmm, it might be commit c3ae62af8e755ea68380fb5ce682e60079a4c388 >> tcp: should drop incoming frames without ACK flag set >> >> It seems RST should be allowed to not have ACK set. >> >> I'll send a fix, thanks ! > > Yes, thats definitely the problem, sorry for that. > > > [PATCH] tcp: accept RST without ACK flag > > commit c3ae62af8e755 (tcp: should drop incoming frames without ACK flag > set) added a regression on the handling of RST messages. > > RST should be allowed to come even without ACK bit set. We validate > the RST by checking the exact sequence, as requested by RFC 793 and > 5961 3.2, in tcp_validate_incoming() > > Reported-by: Eric Wong <[email protected]> > Signed-off-by: Eric Dumazet <[email protected]>
Acked-by: Neal Cardwell <[email protected]> neal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
