diff options
| author | Andreas Born <futur.andy@googlemail.com> | 2017-08-12 00:36:55 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-08-13 20:01:38 -0700 |
| commit | 11e9d7829dd08dbafb24517fe922f11c3a8a9dc2 (patch) | |
| tree | b389255ff179d7d2d325e87c6bf36d2c0ac9c108 /net | |
| parent | fd851ba9caa9a63fdbb72a2e6ed5560c0989e999 (diff) | |
| download | linux-11e9d7829dd08dbafb24517fe922f11c3a8a9dc2.tar.bz2 | |
bonding: ratelimit failed speed/duplex update warning
bond_miimon_commit() handles the UP transition for each slave of a bond
in the case of MII. It is triggered 10 times per second for the default
MII Polling interval of 100ms. For device drivers that do not implement
__ethtool_get_link_ksettings() the call to bond_update_speed_duplex()
fails persistently while the MII status could remain UP. That is, in
this and other cases where the speed/duplex update keeps failing over a
longer period of time while the MII state is UP, a warning is printed
every MII polling interval.
To address these excessive warnings net_ratelimit() should be used.
Printing a warning once would not be sufficient since the call to
bond_update_speed_duplex() could recover to succeed and fail again
later. In that case there would be no new indication what went wrong.
Fixes: b5bf0f5b16b9c (bonding: correctly update link status during mii-commit phase)
Signed-off-by: Andreas Born <futur.andy@googlemail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions