netdev - RE: [PATCH next v3 3/6] bonding: Implement port churn-machine (AD standard 43.4.17).

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] [day] [month] [year] [list]

Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1CAE2BA6@AcuExch.aculab.com>
Date:	Thu, 12 Feb 2015 09:58:19 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Mahesh Bandewar' <maheshb@...gle.com>,
	Jay Vosburgh <j.vosburgh@...il.com>,
	Andy Gospodarek <andy@...yhouse.net>,
	"Veaceslav Falico" <vfalico@...il.com>,
	Nikolay Aleksandrov <nikolay@...hat.com>,
	"David Miller" <davem@...emloft.net>
CC:	Maciej Zenczykowski <maze@...gle.com>,
	netdev <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>
Subject: RE: [PATCH next v3 3/6] bonding: Implement port churn-machine (AD
 standard 43.4.17).

From: Bandewar
> The Chrun Detection machines detect the situation where a port is operable,
      ^^^^^ spelling

> but the Actor and Partner have not attached the link to an Aggregator and
> brought the link into operation within a bound time period. Under normal
> operation of the LACP, aggrement between Actor and Partner should be reached
> very rapidly. Continued failure to reach aggrement can be symptomatic of
> device failure.
...
--
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