sfxge: relax assertion to allow RST flag in TSO packets
Kernel under stress load, mixed MC reboot and sfupdate really generates TSO packet with RST flag. It will generate many TCP packets with RST flag set. May be RST flag should be set in the last segment only, but it could be dropped. So, it is safer to keep the flag in all packets to be sure that connection is reset. Reviewed by: gnn Sponsored by: Solarflare Communications, Inc. MFC after: 2 days Differential Revision: https://reviews.freebsd.org/D2609
This commit is contained in:
parent
d184c1c64f
commit
ca72ba8567
@ -865,8 +865,14 @@ static void tso_start(struct sfxge_tso_state *tso, struct mbuf *mbuf)
|
||||
tso->seqnum = ntohl(th->th_seq);
|
||||
|
||||
/* These flags must not be duplicated */
|
||||
KASSERT(!(th->th_flags & (TH_URG | TH_SYN | TH_RST)),
|
||||
("incompatible TCP flag on TSO packet"));
|
||||
/*
|
||||
* RST should not be duplicated as well, but FreeBSD kernel
|
||||
* generates TSO packets with RST flag. So, do not assert
|
||||
* its absence.
|
||||
*/
|
||||
KASSERT(!(th->th_flags & (TH_URG | TH_SYN)),
|
||||
("incompatible TCP flag 0x%x on TSO packet",
|
||||
th->th_flags & (TH_URG | TH_SYN)));
|
||||
|
||||
tso->out_len = mbuf->m_pkthdr.len - tso->header_len;
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user