Skip to contentSkip to conversation

net: vrf: Fix send to local broadcast address

PATCH In review David Ahern 2 participants 6 messages Jan 25, 2018 – Jan 26, 2018

Subsystems (5)
lore
Share & tools
lore
#0 lore raw

cover net: vrf: Fix send to local broadcast address

Patch set to fix packet send to the 255.255.255.255 address from a VRF.

First patch tell vrf driver to ignore those packets. Second patches updates the uapi to allow sends from sockets bound to an L3 master device.

David Ahern (2):
net: vrf: Add support for sends to local broadcast address net/ipv4: Allow send to local broadcast from a socket bound to a VRF

 drivers/net/vrf.c      |  5 +++--
 net/ipv4/ip_sockglue.c |  6 +++++-
 net/ipv4/raw.c         | 15 ++++++++++++++-
 net/ipv4/udp.c         | 15 ++++++++++++++-
 4 files changed, 36 insertions(+), 5 deletions(-)
Signature · 1 line
2.11.0
#1 lore raw

PATCH 1/2 net: vrf: Add support for sends to local broadcast address

Sukumar reported that sends to the local broadcast address (255.255.255.255) are broken. Check for the address in vrf driver and do not redirect to the VRF device - similar to multicast packets.

With this change sockets can use SO_BINDTODEVICE to specify an egress interface and receive responses. Note: the egress interface can not be a VRF device but needs to be the enslaved device.

https://bugzilla.kernel.org/show_bug.cgi?id=198521

---
Dave: Really this is a day 1 bug that goes back to the beginning of VRF. IMO, backport to the 4.14 LTS kernel is sufficient; the multicast handling for IPv4 was only complete as of the 4.12 kernel. I directed this at net-next because it is not urgent for the 4.15 merge window.

 drivers/net/vrf.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/net/vrf.c +3 -2
index feb1b2e15c2e..139c61c8244a 100644
@@ -673,8 +673,9 @@ static struct sk_buff *vrf_ip_out(struct net_device *vrf_dev,
 				  struct sock *sk,
 				  struct sk_buff *skb)
 {
-	/* don't divert multicast */
-	if (ipv4_is_multicast(ip_hdr(skb)->daddr))
+	/* don't divert multicast or local broadcast */
+	if (ipv4_is_multicast(ip_hdr(skb)->daddr) ||
+	    ipv4_is_lbcast(ip_hdr(skb)->daddr))
 		return skb;
 
 	if (qdisc_tx_is_default(vrf_dev))
Signature · 1 line
2.11.0
maintainer
#2 lore raw

Re: [PATCH net-next 1/2] net: vrf: Add support for sends to local broadcast address

From: David Ahern <[email protected]>
Date: Wed, 24 Jan 2018 19:37:37 -0800

Quoted 11 lines

Sukumar reported that sends to the local broadcast address (255.255.255.255) are broken. Check for the address in vrf driver and do not redirect to the VRF device - similar to multicast packets.

With this change sockets can use SO_BINDTODEVICE to specify an egress interface and receive responses. Note: the egress interface can not be a VRF device but needs to be the enslaved device.

https://bugzilla.kernel.org/show_bug.cgi?id=198521

Quoted 8 lines

---
Dave: Really this is a day 1 bug that goes back to the beginning of VRF. IMO, backport to the 4.14 LTS kernel is sufficient; the multicast handling for IPv4 was only complete as of the 4.12 kernel. I directed this at net-next because it is not urgent for the 4.15 merge window.

You have to decide, either this is for 'net' and -stable, or it isn't.

We don't put things into net-next and then -stable backport it. It doesn't work like that.

#3 lore raw

Re: [PATCH net-next 1/2] net: vrf: Add support for sends to local broadcast address

Quoted 23 lines · David Miller

From: David Ahern <[email protected]>
Date: Wed, 24 Jan 2018 19:37:37 -0800

Quoted 11 lines

Sukumar reported that sends to the local broadcast address (255.255.255.255) are broken. Check for the address in vrf driver and do not redirect to the VRF device - similar to multicast packets.

With this change sockets can use SO_BINDTODEVICE to specify an egress interface and receive responses. Note: the egress interface can not be a VRF device but needs to be the enslaved device.

https://bugzilla.kernel.org/show_bug.cgi?id=198521

Quoted 8 lines

---
Dave: Really this is a day 1 bug that goes back to the beginning of VRF. IMO, backport to the 4.14 LTS kernel is sufficient; the multicast handling for IPv4 was only complete as of the 4.12 kernel. I directed this at net-next because it is not urgent for the 4.15 merge window.

Quoted 5 lines

You have to decide, either this is for 'net' and -stable, or it isn't.

We don't put things into net-next and then -stable backport it. It doesn't work like that.

Please take this one for -net and patch 2 for net-next (it's a new feature). I can re-send as separate patches if needed.

maintainer
#4 lore raw

Re: [PATCH net-next 1/2] net: vrf: Add support for sends to local broadcast address

From: David Ahern <[email protected]>
Date: Thu, 25 Jan 2018 15:01:23 -0700

Quoted 24 lines · David Miller
Quoted 23 lines

From: David Ahern <[email protected]>
Date: Wed, 24 Jan 2018 19:37:37 -0800

Quoted 19 lines

Sukumar reported that sends to the local broadcast address (255.255.255.255) are broken. Check for the address in vrf driver and do not redirect to the VRF device - similar to multicast packets.

With this change sockets can use SO_BINDTODEVICE to specify an egress interface and receive responses. Note: the egress interface can not be a VRF device but needs to be the enslaved device.

https://bugzilla.kernel.org/show_bug.cgi?id=198521

---
Dave: Really this is a day 1 bug that goes back to the beginning of VRF. IMO, backport to the 4.14 LTS kernel is sufficient; the multicast handling for IPv4 was only complete as of the 4.12 kernel. I directed this at net-next because it is not urgent for the 4.15 merge window.

Quoted 7 lines
Quoted 4 lines

You have to decide, either this is for 'net' and -stable, or it isn't.

We don't put things into net-next and then -stable backport it. It doesn't work like that.

Please take this one for -net and patch 2 for net-next (it's a new feature). I can re-send as separate patches if needed.

Ok I'll do that, no need to resend.

Thanks.

#5 lore raw

PATCH 2/2 net/ipv4: Allow send to local broadcast from a socket bound to a VRF

In reply to David Ahern

Message sends to the local broadcast address (255.255.255.255) require uc_index or sk_bound_dev_if to be set to an egress device. However, responses or only received if the socket is bound to the device. This is overly constraining for processes running in an L3 domain. This patch allows a socket bound to the VRF device to send to the local broadcast address by using IP_UNICAST_IF to set the egress interface with packet receipt handled by the VRF binding.

Similar to IP_MULTICAST_IF, relax the constraint on setting IP_UNICAST_IF if a socket is bound to an L3 master device. In this case allow uc_index to be set to an enslaved if sk_bound_dev_if is an L3 master device and is the master device for the ifindex.

In udp and raw sendmsg, allow uc_index to override the oif if uc_index master device is oif (ie., the oif is an L3 master and the index is an L3 slave).

---
 net/ipv4/ip_sockglue.c |  6 +++++-
 net/ipv4/raw.c         | 15 ++++++++++++++-
 net/ipv4/udp.c         | 15 ++++++++++++++-
 3 files changed, 33 insertions(+), 3 deletions(-)
net/ipv4/ip_sockglue.c +5 -1
index 60fb1eb7d7d8..6cc70fa488cb 100644
@@ -808,6 +808,7 @@ static int do_ip_setsockopt(struct sock *sk, int level,
 	{
 		struct net_device *dev = NULL;
 		int ifindex;
+		int midx;
 
 		if (optlen != sizeof(int))
 			goto e_inval;
@@ -823,10 +824,13 @@ static int do_ip_setsockopt(struct sock *sk, int level,
 		err = -EADDRNOTAVAIL;
 		if (!dev)
 			break;
+
+		midx = l3mdev_master_ifindex(dev);
 		dev_put(dev);
 
 		err = -EINVAL;
-		if (sk->sk_bound_dev_if)
+		if (sk->sk_bound_dev_if &&
+		    (!midx || midx != sk->sk_bound_dev_if))
 			break;
 
 		inet->uc_index = ifindex;
net/ipv4/raw.c +14 -1
index 136544b36a46..7c509697ebc7 100644
@@ -617,8 +617,21 @@ static int raw_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
 			ipc.oif = inet->mc_index;
 		if (!saddr)
 			saddr = inet->mc_addr;
-	} else if (!ipc.oif)
+	} else if (!ipc.oif) {
 		ipc.oif = inet->uc_index;
+	} else if (ipv4_is_lbcast(daddr) && inet->uc_index) {
+		/* oif is set, packet is to local broadcast and
+		 * and uc_index is set. oif is most likely set
+		 * by sk_bound_dev_if. If uc_index != oif check if the
+		 * oif is an L3 master and uc_index is an L3 slave.
+		 * If so, we want to allow the send using the uc_index.
+		 */
+		if (ipc.oif != inet->uc_index &&
+		    ipc.oif == l3mdev_master_ifindex_by_index(sock_net(sk),
+							      inet->uc_index)) {
+			ipc.oif = inet->uc_index;
+		}
+	}
 
 	flowi4_init_output(&fl4, ipc.oif, sk->sk_mark, tos,
 			   RT_SCOPE_UNIVERSE,
net/ipv4/udp.c +14 -1
index 853321555a4e..3f018f34cf56 100644
@@ -977,8 +977,21 @@ int udp_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
 		if (!saddr)
 			saddr = inet->mc_addr;
 		connected = 0;
-	} else if (!ipc.oif)
+	} else if (!ipc.oif) {
 		ipc.oif = inet->uc_index;
+	} else if (ipv4_is_lbcast(daddr) && inet->uc_index) {
+		/* oif is set, packet is to local broadcast and
+		 * and uc_index is set. oif is most likely set
+		 * by sk_bound_dev_if. If uc_index != oif check if the
+		 * oif is an L3 master and uc_index is an L3 slave.
+		 * If so, we want to allow the send using the uc_index.
+		 */
+		if (ipc.oif != inet->uc_index &&
+		    ipc.oif == l3mdev_master_ifindex_by_index(sock_net(sk),
+							      inet->uc_index)) {
+			ipc.oif = inet->uc_index;
+		}
+	}
 
 	if (connected)
 		rt = (struct rtable *)sk_dst_check(sk, 0);
Signature · 1 line
2.11.0