From: Robert Shearman <rshearma@brocade.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, David Ahern <dsa@cumulusnetworks.com>,
"Robert Shearman" <rshearma@brocade.com>
Subject: [PATCH net-next 0/3] l3mdev: Improve use with main table
Date: Mon, 10 Apr 2017 15:21:59 +0100 [thread overview]
Message-ID: <1491834122-26252-1-git-send-email-rshearma@brocade.com> (raw)
Attempting to create a TCP socket not bound to a VRF device when a TCP
socket bound to a VRF device with the same port exists (and vice
versa) fails with EADDRINUSE. This limits the ability to use programs
in selected mixed VRF/non-VRF contexts.
This patch series solves the problem by extending the l3mdev be aware
of the special semantics of the main table and fixing issues arising
from the split local/main tables. A VRF master device created linking
to the main table and used for these programs in the same way as those
created for VRF tables can.
Robert Shearman (3):
ipv6: Fix route handling when using l3mdev set to main table
ipv4: Fix route handling when using l3mdev set to main table
l3mdev: Fix lookup in local table when using main table
net/ipv4/af_inet.c | 4 +++-
net/ipv4/fib_frontend.c | 14 +++++++++-----
net/ipv4/raw.c | 5 ++++-
net/ipv6/addrconf.c | 12 +++++++++---
net/ipv6/route.c | 23 ++++++++++++++++++-----
net/l3mdev/l3mdev.c | 26 ++++++++++++++++++++------
6 files changed, 63 insertions(+), 21 deletions(-)
--
2.1.4
next reply other threads:[~2017-04-10 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 14:21 Robert Shearman [this message]
2017-04-10 14:22 ` [PATCH net-next 1/3] ipv6: Fix route handling when using l3mdev set to main table Robert Shearman
2017-04-10 14:22 ` [PATCH net-next 2/3] ipv4: " Robert Shearman
2017-04-10 14:22 ` [PATCH net-next 3/3] l3mdev: Fix lookup in local table when using " Robert Shearman
2017-04-12 16:51 ` [PATCH net-next 0/3] l3mdev: Improve use with " David Ahern
2017-04-13 12:48 ` Robert Shearman
2017-04-13 14:36 ` David Ahern
2017-04-20 13:01 ` Robert Shearman
2017-04-20 14:25 ` David Ahern
2017-04-20 22:36 ` David Ahern
2017-04-21 17:44 ` Robert Shearman
2017-04-21 20:47 ` David Ahern
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=1491834122-26252-1-git-send-email-rshearma@brocade.com \
--to=rshearma@brocade.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.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).