netdev - [PATCH 2/3] net: vlan: handle NETDEV

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1377002752-4622-3-git-send-email-f.fainelli@gmail.com>
Date:	Tue, 20 Aug 2013 13:45:51 +0100
From:	"Florian Fainelli" <f.fainelli@...il.com>
To:	netdev@...r.kernel.org
cc:	amwang@...hat.com, jiri@...nulli.us, stephen@...workplumber.org,
	kaber@...sh.net, davem@...emloft.net, vyasevic@...hat.com,
	johannes@...solutions.net, eric.dumazet@...il.com,
	"Florian Fainelli" <f.fainelli@...il.com>
Subject: [PATCH 2/3] net: vlan: handle NETDEV_CHANGEROOM events

Whenever the parent device has needed_headroom/needed_tailroom
requirement changes, the VLAN devices should also be updated to the new
value. Handle the NETDEV_CHANGEROOM events and just set the new headroom
and tailroom requirements to the values of the parent device.

Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
---
 net/8021q/vlan.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/net/8021q/vlan.c b/net/8021q/vlan.c
index 61fc573..11a1faa 100644
--- a/net/8021q/vlan.c
+++ b/net/8021q/vlan.c
@@ -466,6 +466,13 @@ static int vlan_device_event(struct notifier_block *unused, unsigned long event,
 		vlan_group_for_each_dev(grp, i, vlandev)
 			call_netdevice_notifiers(event, vlandev);
 		break;
+
+	case NETDEV_CHANGEROOM:
+		vlan_group_for_each_dev(grp, i, vlandev) {
+			dev_set_headroom(vlandev, dev->needed_headroom);
+			dev_set_tailroom(vlandev, dev->needed_tailroom);
+		}
+		break;
 	}
 
 out:
-- 
1.8.1.2


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html