On Tue, Jan 17, 2017 at 9:10 PM, Julian Cordes <julian.cordes@xxxxxxxxx> wrote: > Somehow after calling sctp_sendmsg after calling shutdown with SHUT_WR a > resource is not freed anymore. > > I can reproduce the following behaviour: > When running for example the following test case > https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/sender-side-implementation/shutdown-tests/ttl-policy/shutdown-14.pkt > on my machine, it succeeds the first time. This means that the test case > worked as expected. But if I run the same test case > on the same machine again then the bind-call in the test-case will fail. > I waited longer than 30 minutes but only a reboot of the operating > system seems to help in this case. > > See the following test-cases that all reproduce this issue. All call > sctp_sendmsg after calling shutdown, therefore i suspect > that this is the cause of the issue. I think it's a old issue, the latest kernel has no this issue any more. can you give it a try ? > > Testscripts available at: > https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/sender-side-implementation/shutdown-tests/ttl-policy/shutdown-14.pkt > https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/sender-side-implementation/shutdown-tests/ttl-policy/shutdown-1.pkt > https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/sender-side-implementation/shutdown-tests/ttl-policy/shutdown-2.pkt > https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/sender-side-implementation/shutdown-received-tests/ttl-policy/shutdown-1.pkt > https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/sender-side-implementation/shutdown-received-tests/ttl-policy/shutdown-2.pkt -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
