From: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
To: <davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
<yoshfuji@linux-ipv6.org>, <edumazet@google.com>
Cc: <kuniyu@amazon.co.jp>, <kuni1840@gmail.com>,
<netdev@vger.kernel.org>, <osa-contribution-log@amazon.com>
Subject: [PATCH net-next 0/3] Improve bind(addr, 0) behaviour.
Date: Fri, 21 Feb 2020 00:20:17 +0900 [thread overview]
Message-ID: <20200220152020.13056-1-kuniyu@amazon.co.jp> (raw)
Currently we fail to bind sockets to ephemeral ports when all of the ports
are exhausted even if all sockets have SO_REUSEADDR enabled. In this case,
we still have a chance to connect to the different remote hosts.
The second and third patches fix the behaviour to fully utilize all space
of the local (addr, port) tuples.
Kuniyuki Iwashima (3):
tcp: Remove unnecessary conditions in inet_csk_bind_conflict().
tcp: bind(addr, 0) remove the SO_REUSEADDR restriction when ephemeral
ports are exhausted.
tcp: Prevent port hijacking when ports are exhausted
net/ipv4/inet_connection_sock.c | 36 ++++++++++++++++++++++-----------
1 file changed, 24 insertions(+), 12 deletions(-)
--
2.17.2 (Apple Git-113)
next reply other threads:[~2020-02-20 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:20 Kuniyuki Iwashima [this message]
2020-02-20 15:20 ` [PATCH net-next 1/3] tcp: Remove unnecessary conditions in inet_csk_bind_conflict() Kuniyuki Iwashima
2020-02-20 15:20 ` [PATCH net-next 2/3] tcp: bind(addr, 0) remove the SO_REUSEADDR restriction when ephemeral ports are exhausted Kuniyuki Iwashima
2020-02-20 15:20 ` [PATCH net-next 3/3] tcp: Prevent port hijacking when " Kuniyuki Iwashima
2020-02-20 17:11 ` [PATCH net-next 0/3] Improve bind(addr, 0) behaviour David Laight
2020-02-21 10:01 ` Kuniyuki Iwashima
2020-02-21 10:46 ` David Laight
2020-02-20 19:58 ` Eric Dumazet
2020-02-21 20:35 ` [PATCH net-next 0/3] ImpArove " Kuniyuki Iwashima
2020-02-22 1:07 ` [PATCH net-next 0/3] Improve " Kuniyuki Iwashima
2020-02-23 21:06 ` Kuniyuki Iwashima
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=20200220152020.13056-1-kuniyu@amazon.co.jp \
--to=kuniyu@amazon.co.jp \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuni1840@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=osa-contribution-log@amazon.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;
as well as URLs for NNTP newsgroup(s).