From: Daniel Borkmann <dborkman@redhat.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Problem gettting lksctp-tools 1.0.15 func_tests to work on CentOS 6.4
Date: Wed, 06 Nov 2013 14:35:40 +0000 [thread overview]
Message-ID: <527A53BC.8050207@redhat.com> (raw)
In-Reply-To: <023d1910869240e5be263d397c83042f@LWLEXCHMBX01.olympus.F5Net.com>
On 11/06/2013 03:16 PM, Jeff Carter wrote:
> I've installed lksctp-tools-1.0.15 on a CentOS 6.4 system with the following kernel:
>
> Linux version 2.6.32-358.6.1.el6.x86_64 (mockbuild@c6b9.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Tue Apr 23 19:29:00 UTC 2013
>
> When I attempt to build/run the v4test, I get failures in test_sockopt, test_tcp_style, test_1_to_1_send, and test_1_to_1_sendmsg.
Which errors concretely?
> Also, a "successful" run of the test suite results in the kernel logging these messages:
>
> Nov 6 05:49:16 kernel: SCTP: Use of int in maxseg socket option deprecated
> Nov 6 05:49:16 kernel: SCTP: Use struct sctp_assoc_value instead
>
> All the failing tests report "BROK : bind: Address already in use". With test_sockopt, it is at step 5. It appears that it is trying to set up a new set of client/server sockets immediately after closing the sockets from the previous test, but using the same IP/port.
Yep, there's an upstream fix that you are missing:
commit 8c98653f05534acd1cb07ea4929702a3659177d1
Author: Daniel Borkmann <dborkman@redhat.com>
Date: Fri Feb 1 04:37:43 2013 +0000
sctp: sctp_close: fix release of bindings for deferred call_rcu's
> Is the correct change more likely to be adding SO_REUSEADDR, or moving each test to its own set of ports?
>
> Jeff Carter
prev parent reply other threads:[~2013-11-06 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 14:16 Problem gettting lksctp-tools 1.0.15 func_tests to work on CentOS 6.4 Jeff Carter
2013-11-06 14:35 ` Daniel Borkmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527A53BC.8050207@redhat.com \
--to=dborkman@redhat.com \
--cc=linux-sctp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.