netdev - Re: [PATCH v2] bonding: force enable lacp port after link state recovery for 802.3ad

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: <20190827.150456.509211205582645335.davem@davemloft.net>
Date:   Tue, 27 Aug 2019 15:04:56 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     zhangsha.zhang@...wei.com
Cc:     j.vosburgh@...il.com, vfalico@...il.com, andy@...yhouse.net,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        yuehaibing@...wei.com, hunongda@...wei.com, alex.chen@...wei.com
Subject: Re: [PATCH v2] bonding: force enable lacp port after link state
 recovery for 802.3ad

From: <zhangsha.zhang@...wei.com>
Date: Fri, 23 Aug 2019 11:42:09 +0800

> - If speed/duplex getting failed here, the link status
>   will be changed to BOND_LINK_FAIL;

How does it fail at this step?  I suspect this is a driver specific
problem.