netdev - Re: [patch net-next V8] net: introduce ethernet teaming device

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: <20111114213749.GB2250@minipsycho>
Date:	Mon, 14 Nov 2011 22:37:49 +0100
From:	Jiri Pirko <jpirko@...hat.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Andy Gospodarek <andy@...yhouse.net>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	bhutchings@...arflare.com, shemminger@...tta.com, fubar@...ibm.com,
	tgraf@...radead.org, ebiederm@...ssion.com, mirqus@...il.com,
	kaber@...sh.net, greearb@...delatech.com, jesse@...ira.com,
	fbl@...hat.com, benjamin.poirier@...il.com, jzupka@...hat.com,
	ivecera@...hat.com
Subject: Re: [patch net-next V8] net: introduce ethernet teaming device

Mon, Nov 14, 2011 at 07:17:52PM CET, eric.dumazet@...il.com wrote:
>Le lundi 14 novembre 2011 à 12:31 -0500, Andy Gospodarek a écrit :
>
>> I'm a bit surprised by this.  Not only is this new function currently
>> difficult to setup (it took me over an hour to go from a a fresh F16
>> install to one that had all the necessary libraries and tools to even
>> configure a team device for the first time), but I was able to cause an
>> Oops with v8 in only a few minutes of testing.
>> 
>> I have no problem with this functionality as an add-on and possibly
>> future replacement to some of what currently exists with bonding, but it
>> seems like what is included in the initial support should should:
>> 
>> 1. Not panic easily.
>> 2. Have userspace bits in place to actually test all the proposed kernel
>> code.  (Jiri admits there is no way to verify the active-backup code).
>> 3. Have some known, published test results.
>> 
>> I hope Jiri will reconsider having a separate team tree for the next few
>> weeks or months until these issues are worked out.  I think the hard
>> work will pay off and it is close to being ready; it just doesn't seem
>> like it is right now.
>> 
>
>Its marked EXPERIMENTAL, so probably some changes are expected before
>production mode :)

Exactly. The primary goal was to get this broader audience so people
use this and find bugs, like you did Andy :)
>
>
>
--
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