From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Tobias S. Josefowitz" <t.josefowitz@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: binding UDP port 0 with SO_REUSEADDR
Date: Wed, 01 Aug 2012 21:02:56 +0200 [thread overview]
Message-ID: <1343847776.21269.797.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAEZM=bNdyZoTiGYwNM_3v+ro7dEn0q9aTo4040tBDqDSH3HOXg@mail.gmail.com>
On Wed, 2012-08-01 at 13:36 +0200, Tobias S. Josefowitz wrote:
> Hey all,
>
> I recently noticed that binding UDP port 0 with SO_REUSEADDR yields
> unexpected results for me - the kernel occasionally gives out UDP
> ports used by other processes, if they were bound with SO_REUSEADDR,
> too.
>
> I did some digging, it seems that
> f24d43c07e208372aa3d3bff419afbf43ba87698 introduced this behaviour.
> I'm not at all sure if this could/should be called a bug, but I need
> to say, it was severly unexpected at my side, and that probably goes
> for others, too.
>
> Just bringing this to your attention, I have no suggestions on it whatsoever.
And why are you using SO_REUSEADDR on UDP unicast sockets ?
I mean, this is exactly saying " By using this REUSEADDR, I am allowing
this port being used by another process, even from another user"
next prev parent reply other threads:[~2012-08-01 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 11:36 binding UDP port 0 with SO_REUSEADDR Tobias S. Josefowitz
2012-08-01 19:02 ` Eric Dumazet [this message]
2012-08-01 19:38 ` Tobias S. Josefowitz
2012-08-02 16:33 ` Tobias S. Josefowitz
2012-08-02 16:57 ` Eric Dumazet
2012-08-02 19:05 ` Tobias S. Josefowitz
2012-08-21 9:09 ` Jan Engelhardt
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=1343847776.21269.797.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=t.josefowitz@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