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

2019-08-29 Thread zhangsha (A)
> Chenzhendong (alex) > Subject: Re: [PATCH v2] bonding: force enable lacp port after link state > recovery for 802.3ad > > From: > Date: Fri, 23 Aug 2019 11:42:09 +0800 > > > - If speed/duplex getting failed here, the link status > > will be changed to BOND_LIN

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

2019-08-28 Thread David Miller
You've had enough time to respon to my feedback question. I'm tossing this patch.

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

2019-08-27 Thread David Miller
From: 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.

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

2019-08-22 Thread zhangsha.zhang
From: Sha Zhang After the commit 334031219a84 ("bonding/802.3ad: fix slave link initialization transition states") merged, the slave's link status will be changed to BOND_LINK_FAIL from BOND_LINK_DOWN in the following scenario: - Driver reports loss of carrier and bonding driver receives