From: Paul Gofman <pgofman@codeweavers.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
"open list:NETWORKING [TCP]" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [RFC] EADDRINUSE from bind() on application restart after killing
Date: Fri, 14 Oct 2022 12:20:37 -0500 [thread overview]
Message-ID: <03031c84-baa0-fe99-b1d7-44963cad0001@codeweavers.com> (raw)
In-Reply-To: <CANn89iKoaLRupASAJKW5ZprXhSMiXSs7vi5UT=wEU11R5+iLZQ@mail.gmail.com>
On 10/14/22 11:45, Eric Dumazet wrote:
> On Fri, Oct 14, 2022 at 9:39 AM Paul Gofman <pgofman@codeweavers.com> wrote:
>
> I think it is documented.
>
> man 7 socket
>
> SO_REUSEADDR
> Indicates that the rules used in validating addresses
> supplied in a bind(2) call should allow reuse of local addresses. For
> AF_INET sockets this means
> that a socket may bind, except when there is an active
> listening socket bound to the address. When the listening socket is
> bound to INADDR_ANY with a
> specific port then it is not possible to bind to this
> port for any local address. Argument is an integer boolean flag.
>
> You seem to need another way, so you will have to ask this question in IETF.
Thanks a lot, I think it answers my question, I am afraid I was reading
this a bit wrong.
prev parent reply other threads:[~2022-10-14 17:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 8:18 [RFC] EADDRINUSE from bind() on application restart after killing Muhammad Usama Anjum
2022-05-24 22:13 ` Eric Dumazet
2022-05-30 13:15 ` Muhammad Usama Anjum
2022-05-30 15:28 ` Eric Dumazet
2022-06-27 10:20 ` Muhammad Usama Anjum
2022-06-27 11:47 ` Eric Dumazet
2022-09-30 13:24 ` Muhammad Usama Anjum
2022-09-30 15:16 ` Eric Dumazet
2022-10-14 15:52 ` Paul Gofman
2022-10-14 16:20 ` Eric Dumazet
2022-10-14 16:31 ` Paul Gofman
2022-10-14 16:34 ` Eric Dumazet
2022-10-14 16:39 ` Paul Gofman
2022-10-14 16:45 ` Eric Dumazet
2022-10-14 17:20 ` Paul Gofman [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=03031c84-baa0-fe99-b1d7-44963cad0001@codeweavers.com \
--to=pgofman@codeweavers.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=usama.anjum@collabora.com \
--cc=yoshfuji@linux-ipv6.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