All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Mike Manning <mmanning@vyatta.att-mail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net] ipv6: Consider sk_bound_dev_if when binding a raw socket to an address
Date: Mon, 20 May 2019 16:16:20 -0600	[thread overview]
Message-ID: <8b6e12cf-08b7-d625-325e-ffacf3db7f26@gmail.com> (raw)
In-Reply-To: <20190520185717.24914-1-mmanning@vyatta.att-mail.com>

On 5/20/19 12:57 PM, Mike Manning wrote:
> IPv6 does not consider if the socket is bound to a device when binding
> to an address. The result is that a socket can be bound to eth0 and
> then bound to the address of eth1. If the device is a VRF, the result
> is that a socket can only be bound to an address in the default VRF.
> 
> Resolve by considering the device if sk_bound_dev_if is set.
> 
> Signed-off-by: Mike Manning <mmanning@vyatta.att-mail.com>
> ---
>  net/ipv6/raw.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/net/ipv6/raw.c b/net/ipv6/raw.c
> index 84dbe21b71e5..96a3559f2a09 100644
> --- a/net/ipv6/raw.c
> +++ b/net/ipv6/raw.c
> @@ -287,7 +287,9 @@ static int rawv6_bind(struct sock *sk, struct sockaddr *uaddr, int addr_len)
>  			/* Binding to link-local address requires an interface */
>  			if (!sk->sk_bound_dev_if)
>  				goto out_unlock;
> +		}
>  
> +		if (sk->sk_bound_dev_if) {
>  			err = -ENODEV;
>  			dev = dev_get_by_index_rcu(sock_net(sk),
>  						   sk->sk_bound_dev_if);
> 

Reviewed-by: David Ahern <dsahern@gmail.com>
Tested-by: David Ahern <dsahern@gmail.com>

  reply	other threads:[~2019-05-20 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 18:57 [PATCH net] ipv6: Consider sk_bound_dev_if when binding a raw socket to an address Mike Manning
2019-05-20 22:16 ` David Ahern [this message]
2019-05-21 20:13 ` 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=8b6e12cf-08b7-d625-325e-ffacf3db7f26@gmail.com \
    --to=dsahern@gmail.com \
    --cc=mmanning@vyatta.att-mail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.