netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neal Cardwell <ncardwell@google.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	"Michael Kerrisk" <mtk.manpages@gmail.com>,
	"Maciej Żenczykowski" <maze@google.com>
Subject: Re: [PATCH net-next] inet: add IP_BIND_ADDRESS_NO_PORT to overcome bind(0) limitations
Date: Sat, 6 Jun 2015 22:30:07 -0400	[thread overview]
Message-ID: <CADVnQy=qbyTUdCPvDv8UbcuXJAsNhQVSiJCo83e9k8s8OWOF8w@mail.gmail.com> (raw)
In-Reply-To: <1433605985.1895.84.camel@edumazet-glaptop2.roam.corp.google.com>

On Sat, Jun 6, 2015 at 11:53 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> From: Eric Dumazet <edumazet@google.com>
...
> This patch adds a new SOL_IP socket option, asking kernel to ignore
> the 0 port provided by application in bind(IP, port=0) and only
> remember the given IP address.
...
> This new feature is available for both IPv4 and IPv6.

I like this a lot. This addresses a very serious gap in the sockets
API, and should be very useful. The comment mentions that this is
available for IPv6. From skimming the change I would have expected
inet6_bind() would need a change analogous to the change in
inet_bind()? Was there a missing "git add", or is a change to
inet6_bind() somehow not needed?

Thanks!

neal

  parent reply	other threads:[~2015-06-07  2:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 15:53 [PATCH net-next] inet: add IP_BIND_ADDRESS_NO_PORT to overcome bind(0) limitations Eric Dumazet
2015-06-06 16:38 ` Maciej Żenczykowski
2015-06-06 17:39   ` Eric Dumazet
2015-06-06 19:40   ` David Miller
2015-06-07  2:30 ` Neal Cardwell [this message]
2015-06-07  3:08   ` Eric Dumazet
2015-06-07  4:17   ` [PATCH v2 " Eric Dumazet
2015-06-07  6:57     ` David Miller

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='CADVnQy=qbyTUdCPvDv8UbcuXJAsNhQVSiJCo83e9k8s8OWOF8w@mail.gmail.com' \
    --to=ncardwell@google.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=maze@google.com \
    --cc=mtk.manpages@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).