diff options
author | Xin Long <lucien.xin@gmail.com> | 2016-09-14 02:04:21 +0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-09-18 22:02:32 -0400 |
commit | 645194409b0634a43890ec27c491c368b3bffc07 (patch) | |
tree | e64bb7b29a159f3030f3b4da7498e8af4c9ea9b3 /include | |
parent | b61c654f9b3f1a271217e46c893f80565b1f754d (diff) |
sctp: save transmit error to sk_err in sctp_outq_flush
Every time when sctp calls sctp_outq_flush, it sends out the chunks of
control queue, retransmit queue and data queue. Even if some trunks are
failed to transmit, it still has to flush all the transports, as it's
the only chance to clean that transmit_list.
So the latest transmit error here should be returned back. This transmit
error is an internal error of sctp stack.
I checked all the places where it uses the transmit error (the return
value of sctp_outq_flush), most of them are actually just save it to
sk_err.
Except for sctp_assoc/endpoint_bh_rcv, they will drop the chunk if
it's failed to send a REPLY, which is actually incorrect, as we can't
be sure the error that sctp_outq_flush returns is from sending that
REPLY.
So it's meaningless for sctp_outq_flush to return error back.
This patch is to save transmit error to sk_err in sctp_outq_flush, the
new error can update the old value. Eventually, sctp_wait_for_* would
check for it.
Signed-off-by: Xin Long <lucien.xin@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions