From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Yasevich <vyasevich@gmail.com>, Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Fw: [Bug 104301] New: Connect failure on sctp socket under debug
Date: Wed, 9 Sep 2015 07:47:59 -0700 [thread overview]
Message-ID: <20150909074759.1e256966@urahara> (raw)
Begin forwarded message:
Date: Wed, 9 Sep 2015 13:57:38 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 104301] New: Connect failure on sctp socket under debug
https://bugzilla.kernel.org/show_bug.cgi?id=104301
Bug ID: 104301
Summary: Connect failure on sctp socket under debug
Product: Networking
Version: 2.5
Kernel Version: 3.13.0-63-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: riccardomanfrin@gmail.com
Regression: No
When starting an sctp client with gdb, I experience a connect failure (-1 is
returned), with errno 106 (Transport endpoint is already connected).
If I then cat /proc/net/sctp/assocs, I see the connection and I see the
successful handshake on wireshark.
If I ignore the connect failure, and pretend I'm actually connected, I can send
and receive packets without any trouble.
The same client application, run not-under-gdb, does not exhibits the issue and
the connect returns 0.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-09-09 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150909074759.1e256966@urahara \
--to=stephen@networkplumber.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox