Red Hat Bugzilla – Bug 495318
Bonding driver updelay parameter actual behavior doesn't match documented behavior
Last modified: 2015-05-04 21:16:41 EDT
Created attachment 339193 [details]
Removes the updelay for the first slave to become active
Description of problem:
The Linux kernel documentation in the kernel-doc package at Documentation/networking/bonding.txt states:
"Note that when a bonding interface has no active links, the
driver will immediately reuse the first link that goes up, even if the
updelay parameter has been specified (the updelay is ignored in this
case). If there are slave interfaces waiting for the updelay timeout
to expire, the interface that first went into that state will be
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure an active-passive bond interface with updelay set to something appropriately large (30000 or 60000)
2. From a state where the bond device and both links are up, remove both links.
3. Reconnect one,
4. Wait for the updelay to time out before the bond device returns to an operational state.
When no slaves have active links I would expect the bond device to immediately become operational after the first link-up on any slave.
I have tested this patch and it seems to do the right thing. I have only tested this in an active-passive bonding configuration.
I have also sent a patch to the bonding maintainer (email@example.com) listed in MAINTAINERS rebased against 18.104.22.168 earlier today (but have not heard back from him yet).
Created attachment 340946 [details]
Correct version of the patch
NOTE: The original patch was accidentally a reverse diff. This should be a correct, forward, patch. Thanks to my coworker who was reviewing the bug and patch and asked me why I was removing the or clause... oops.
patch applied to net-next-2.6:
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.