diff options
author | Xin Long <lucien.xin@gmail.com> | 2016-07-30 15:00:45 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-08-01 23:32:50 +0300 |
commit | df7e88f6cad8cc4e02c9275018a572fab59562c0 (patch) | |
tree | 6674ed64619f4888ed1f2ebcdb502e3e498e6cc6 /drivers/net/caif | |
parent | ecd5a32318280133e8ae93f10ea693293a04a786 (diff) | |
download | linux-df7e88f6cad8cc4e02c9275018a572fab59562c0.tar.xz |
sctp: change to use TCP_CLOSE_WAIT as SCTP_SS_CLOSING
Prior to this patch, sctp defined TCP_CLOSING as SCTP_SS_CLOSING.
TCP_CLOSING is such a special sk state in TCP that inet common codes
even exclude it.
For instance, inet_accept thinks the accept sk's state never be
TCP_CLOSING, or it will give a WARN_ON. TCP works well with that
while SCTP may trigger the call trace, as CLOSING state in SCTP
has different meaning from TCP.
This fix is to change to use TCP_CLOSE_WAIT as SCTP_SS_CLOSING,
instead of TCP_CLOSING. Some side-effects could be expected,
regardless of not being used before. inet_accept will accept it
now.
I did all the func_tests in lksctp-tools and ran sctp codnomicon
fuzzer tests against this patch, no regression or failure found.
Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/caif')
0 files changed, 0 insertions, 0 deletions