netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, david@opensourcerouting.org, equinox@diac24.net
Subject: Re: [PATCH net-next v2 2/2] net: l3mdev: prefer VRF master for source address selection
Date: Wed, 24 Feb 2016 14:16:39 -0500 (EST)	[thread overview]
Message-ID: <20160224.141639.1732481853660602743.davem@davemloft.net> (raw)
In-Reply-To: <1456165431-867-2-git-send-email-dsa@cumulusnetworks.com>

From: David Ahern <dsa@cumulusnetworks.com>
Date: Mon, 22 Feb 2016 10:23:51 -0800

> From: David Lamparter <equinox@diac24.net>
> 
> When selecting an address in context of a VRF, the vrf master should be
> preferred for address selection.  If it isn't, the user has a hard time
> getting the system to select to their preference - the code will pick
> the address off the first in-VRF interface it can find, which on a
> router could well be a non-routable address.
> 
> Signed-off-by: David Lamparter <equinox@diac24.net>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
> [dsa: Fixed comment style ]
> ---
> v2
> - Fixed comment per Dave's response
> 
>  net/ipv4/devinet.c | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
> index 614904c29cbd..01119fbf3b30 100644
> --- a/net/ipv4/devinet.c
> +++ b/net/ipv4/devinet.c
> @@ -1217,6 +1217,24 @@ __be32 inet_select_addr(const struct net_device *dev, __be32 dst, int scope)
>  no_in_dev:
>  	master_idx = l3mdev_master_ifindex_rcu(dev);
>  
> +	/* For VRFs, the VRF device takes the place of the loopback device,
> +	 * with addresses on it being preferred.  Note in such cases the
> +	 * loopback device will be among the devices that fail the master_idx
> +	 * equality check in the loop below.
> +	 */
> +	if (master_idx &&
> +	    (dev = dev_get_by_index_rcu(net, master_idx)) &&
> +	    (in_dev = __in_dev_get_rcu(dev))) {
> +
> +		for_primary_ifa(in_dev) {

Please get rid of this empty line, and resubmit this series with a proper
"0/N" header posting explaining the high level purpose of this patch
series and what it is doing.

Thanks.

      reply	other threads:[~2016-02-24 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 18:23 [PATCH net-next 1/2] net: l3mdev: address selection should only consider devices in L3 domain David Ahern
2016-02-22 18:23 ` [PATCH net-next v2 2/2] net: l3mdev: prefer VRF master for source address selection David Ahern
2016-02-24 19:16   ` David Miller [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=20160224.141639.1732481853660602743.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=david@opensourcerouting.org \
    --cc=dsa@cumulusnetworks.com \
    --cc=equinox@diac24.net \
    --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).