netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <t.artem@lycos.com>
To: eric.dumazet@gmail.com
Cc: stephen@networkplumber.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: A call to revise sockets behaviour
Date: Mon, 29 Jul 2013 18:02:16 +0000 (UTC)	[thread overview]
Message-ID: <2134648871.43175.1375120936132.JavaMail.mail@webmail09> (raw)
In-Reply-To: 1375119778.10515.20.camel@edumazet-glaptop

Jul 29, 2013 11:43:00 PM, Eric wrote:
On Mon, 2013-07-29 at 15:47 +0000, Artem S. Tashkinov wrote:
>
>> A wine developer clearly showed that this option simply doesn't work. 
>> 
>> http://bugs.winehq.org/show_bug.cgi?id=26031#c21
>> 
>> Output of strace:
>> getsockopt(24, SOL_SOCKET, SO_REUSEADDR, [0], [4]) = 0
>> setsockopt(24, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
>> bind(24, {sa_family=AF_INET, sin_port=htons(43012), sin_addr=inet_addr("0.     
>> 0.0.0")}, 16) = -1 EADDRINUSE (Address already in use)
>
>Its clear that some other socket did not use SO_REUSADDR
>
>All sockets using a given port _must_ have use SO_REUSADDR to allow this
>port being reused.
>

It's exactly what's been tried. A program running with SO_REUSADDR, once no longer
running consequently fails to regain the rights for the port.

  reply	other threads:[~2013-07-29 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 15:10 A call to revise sockets behaviour Artem S. Tashkinov
2013-07-29 15:35 ` Stephen Hemminger
2013-07-29 15:47   ` Artem S. Tashkinov
2013-07-29 17:26     ` Rick Jones
2013-07-29 17:31       ` Artem S. Tashkinov
2013-07-29 17:42     ` Eric Dumazet
2013-07-29 18:02       ` Artem S. Tashkinov [this message]
2013-07-29 19:00         ` John Heffner

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=2134648871.43175.1375120936132.JavaMail.mail@webmail09 \
    --to=t.artem@lycos.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).