netdev - Re: [PATCH net-next v2 0/3] switchdev: support stp updates on stacked netdevices

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: <20150313.123156.2118585119289960334.davem@davemloft.net>
Date:	Fri, 13 Mar 2015 12:31:56 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	roopa@...ulusnetworks.com
Cc:	sfeldma@...il.com, jiri@...nulli.us, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/3] switchdev: support stp updates on
 stacked netdevices

From: roopa <roopa@...ulusnetworks.com>
Date: Fri, 13 Mar 2015 06:25:24 -0700

> David, if you mean not touch bond and team but have the switchdev
> api do it transparently, yes, i had it that way initially.  And i do
> liked it that way as well. But the feedback i received (during the
> initial introduction of this for setlink/dellink) was to make it
> explicit for each master.

I think the concern is that we only want to do this for devices
for which it is safe to "traverse" down like this.

But frankly I cannot think of any layered device where we would
not want to do this.

Let's go back to the simple scheme where we unconditionally traverse
and if we hit a problem case we'll figure out how to deal with it
then, ok?
--
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