diff options
author | Neil Horman <nhorman@tuxdriver.com> | 2013-01-17 11:15:08 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2013-01-17 18:39:56 -0500 |
commit | 2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86 (patch) | |
tree | 6f634d10b8bd5620acdab7b34d05728aed9cea05 /drivers/net/ethernet/calxeda | |
parent | 01fe944f1024bd4e5c327ddbe8d657656b66af2f (diff) | |
download | linux-2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86.tar.gz linux-2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86.tar.bz2 linux-2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86.zip |
sctp: refactor sctp_outq_teardown to insure proper re-initalization
Jamie Parsons reported a problem recently, in which the re-initalization of an
association (The duplicate init case), resulted in a loss of receive window
space. He tracked down the root cause to sctp_outq_teardown, which discarded
all the data on an outq during a re-initalization of the corresponding
association, but never reset the outq->outstanding_data field to zero. I wrote,
and he tested this fix, which does a proper full re-initalization of the outq,
fixing this problem, and hopefully future proofing us from simmilar issues down
the road.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Reported-by: Jamie Parsons <Jamie.Parsons@metaswitch.com>
Tested-by: Jamie Parsons <Jamie.Parsons@metaswitch.com>
CC: Jamie Parsons <Jamie.Parsons@metaswitch.com>
CC: Vlad Yasevich <vyasevich@gmail.com>
CC: "David S. Miller" <davem@davemloft.net>
CC: netdev@vger.kernel.org
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/calxeda')
0 files changed, 0 insertions, 0 deletions