From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 76521] New: no-blocking socket can send data through non-existent local port
Date: Wed, 21 May 2014 06:56:05 +0900 [thread overview]
Message-ID: <20140521065605.0955afb7@samsung-9> (raw)
Begin forwarded message:
Date: Mon, 19 May 2014 18:21:19 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 76521] New: no-blocking socket can send data through non-existent local port
https://bugzilla.kernel.org/show_bug.cgi?id=76521
Bug ID: 76521
Summary: no-blocking socket can send data through non-existent
local port
Product: Networking
Version: 2.5
Kernel Version: 3.11.0-15
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: billhong1998@gmail.com
Regression: No
Created attachment 136811
--> https://bugzilla.kernel.org/attachment.cgi?id=136811&action=edit
Run code to reproduce the issue
The attached code is a epoll network client supposed to test a network server
in high traffic case. Multiple threads create non-blocking sockets to simulate
heavy network load. Most sockets work well, but occasionally some sockets can
send data via non-existent local port, and can read data from the port as well.
Maybe I am not acquainted enough with epoll networking programming, and even
not sure if it is a bug in no-blocking i/o or epoll, and also not certain which
websites are the right place to discuss epoll or no-blocking i/o technologies.
Anyone has any ideas would be greatly appreciated. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2014-05-20 22:00 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=20140521065605.0955afb7@samsung-9 \
--to=stephen@networkplumber.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox