netdev - Re: [PATCH next 0/3] re-org actor admin/oper key updates

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: <20151102.225240.1162453078430872461.davem@davemloft.net>
Date:	Mon, 02 Nov 2015 22:52:40 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	maheshb@...gle.com
Cc:	j.vosburgh@...il.com, andy@...yhouse.net, vfalico@...il.com,
	nikolay@...hat.com, decot@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH next 0/3] re-org actor admin/oper key updates

From: Mahesh Bandewar <maheshb@...gle.com>
Date: Sat, 31 Oct 2015 12:44:55 -0700

> I was observing machines entering into weird LACP state when the
> partner is in passive mode. This issue is not because of the partners
> in passive state but probably because of some operational key update
> which is pushing the state-machine is that weird state. This was
> happening randomly on about 1% of the machine (when the sample size
> is a large set of machines with a variety of NICs/ports bonded).
> 
> In this patch-series I'm attempting to unify the logic of actor-key
> / operational-key changes to one place to avoid possible errors in
> update. Also this eliminates the need for the event-handler to decide
> if the key needs update.
> 
> After this patch-set none of the machines (from same sample set) were
> exhibiting LACP-weirdness that was observed earlier.

Series applied, thanks.
--
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