netdev - Re: [PATCH net-next v6 11/23] switchdev: add new switchdev bridge setlink

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: <20150509184851.GC2290@nanopsycho>
Date:	Sat, 9 May 2015 20:48:51 +0200
From:	Jiri Pirko <jiri@...nulli.us>
To:	sfeldma@...il.com
Cc:	netdev@...r.kernel.org, roopa@...ulusnetworks.com,
	linux@...ck-us.net, f.fainelli@...il.com, andrew@...n.ch,
	simon.horman@...ronome.com, joe@...ches.com,
	sridhar.samudrala@...el.com, ronen.arad@...el.com
Subject: Re: [PATCH net-next v6 11/23] switchdev: add new switchdev bridge
 setlink

Sat, May 09, 2015 at 07:40:13PM CEST, sfeldma@...il.com wrote:
>From: Scott Feldman <sfeldma@...il.com>
>
>Add new switchdev_port_bridge_setlink that can be used by drivers
>implementing .ndo_bridge_setlink to set switchdev bridge attributes.
>Basically turn the raw rtnl_bridge_setlink netlink into switchdev attr
>sets.  Proper netlink attr policy checking is done on the protinfo part of
>the netlink msg.
>
>Currently, for protinfo, only bridge port attrs BR_LEARNING and
>BR_LEARNING_SYNC are parsed and passed to port driver.
>
>For afspec, VLAN objs are passed so switchdev driver can set VLANs assigned
>to SELF.  To illustrate with iproute2 cmd, we have:
>
>	bridge vlan add vid 10 dev sw1p1 self master
>
>To add VLAN 10 to port sw1p1 for both the bridge (master) and the device
>(self).
>
>Signed-off-by: Scott Feldman <sfeldma@...il.com>

Acked-by: Jiri Pirko <jiri@...nulli.us>
--
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