projects / dragonfly.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b58f1e6) | patch
tcp: Don't panic if persist timer is started in CLOSED and TERMINATING
authorSepherosa Ziehau <sephe@dragonflybsd.org>
Sat, 15 Jan 2011 12:02:34 +0000 (20:02 +0800)
committerSepherosa Ziehau <sephe@dragonflybsd.org>
Sat, 15 Jan 2011 12:09:32 +0000 (20:09 +0800)
commitc529614ee0060246d8d1464c8f7dbea0e9f8c46b
tree6dee937c0b298c9c7f9a909061d7516158493106tree | snapshot
parentb58f1e66e1cfc051239a06ce5ea687db78a50f40commit | diff
tcp: Don't panic if persist timer is started in CLOSED and TERMINATING

Persistent timer could go wrong only when SYN is to be turned on in
tcp_output(), however, CLOSED and TERMINATING states' flags does not
contain SYN at all.  And starting persistent timer in CLOSED state is
absolutely valid, e.g. from tcp_drop()

Reported-by: dillon@
sys/netinet/tcp_output.c diff | blob | blame | history
DragonFly Project Source