netdev - RE: [RFC PATCH net-next] bonding: Use notifiers for slave link state detection

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: <87618083B2453E4A8714035B62D679925050766D@FMSMSX105.amr.corp.intel.com>
Date:	Wed, 13 Jan 2016 17:03:17 +0000
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Jay Vosburgh <jay.vosburgh@...onical.com>
CC:	"zyjzyj2000@...il.com" <zyjzyj2000@...il.com>,
	"mkubecek@...e.cz" <mkubecek@...e.cz>,
	"vfalico@...il.com" <vfalico@...il.com>,
	"gospo@...ulusnetworks.com" <gospo@...ulusnetworks.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Shteinbock, Boris (Wind River)" <boris.shteinbock@...driver.com>
Subject: RE: [RFC PATCH net-next] bonding: Use notifiers for slave link
 state detection

>-----Original Message-----
>From: Jay Vosburgh [mailto:jay.vosburgh@...onical.com]
>Sent: Friday, January 08, 2016 6:20 PM
>To: Tantilov, Emil S
>Cc: zyjzyj2000@...il.com; mkubecek@...e.cz; vfalico@...il.com;
>gospo@...ulusnetworks.com; netdev@...r.kernel.org; Shteinbock, Boris (Wind
>River)
>Subject: Re: [RFC PATCH net-next] bonding: Use notifiers for slave link
>state detection
>
>Tantilov, Emil S <emil.s.tantilov@...el.com> wrote:
>
>>>-----Original Message-----
>>From: Jay Vosburgh [mailto:jay.vosburgh@...onical.com]
>>>Sent: Thursday, January 07, 2016 5:29 PM
>>>Subject: [RFC PATCH net-next] bonding: Use notifiers for slave link state
>>>detection
>>>
>>>
>>>	TEST PATCH
>>>
>>>	This patch modifies bonding to utilize notifier callbacks to
>>>detect slave link state changes.  It is intended to be used with miimon
>>>set to zero, and does not support the updelay or downdelay options to
>>>bonding.  It's not as complicated as it looks; most of the change set is
>>>to break out the inner loop of bond_miimon_inspect into its own
>>>function.
>>
>>Jay,
>>
>>I managed to do a quick test with this patch and occasionally there is
>>a case where I see the bonding driver reporting link up for an
>>interface (eth1) that is not up just yet:
>[...]
>>[12985.213752] ixgbe 0000:01:00.0 eth0: NIC Link is Up 10 Gbps, Flow
>Control: RX/TX
>>[12985.213970] bond0: link status definitely up for interface eth0, 10000
>Mbps full duplex
>>[12985.213975] bond0: link status definitely up for interface eth1, 0 Mbps
>full duplex
>
>	Thanks for testing; the misbehavior is because I cheaped out and
>didn't break out the commit function into a "single slave" version.  The
>below patch (against net-next, replacing the original patch) shouldn't
>generate the erroneous additional link messages any more.
>
>	This does generate an RCU warning, although the code actually is
>safe (since the notifier callback holds RTNL); I'll sort that out next
>week.
>
>	-J

Alright, so I was able to kick off another test with this patch and it's
been running for 24 hours+ without errors. The setup I have has all kinds of
link issues, so it's a pretty good stress test.

Note that the issue that started this thread was due to the ixgbe driver 
reporting speed directly from the LINKS register, which is no longer the case,
so just using notifiers is probably not enough to get around this issue, but
this should not be a problem anymore (at least for ixgbe).

Thanks,
Emil