From: David Miller <davem@davemloft.net>
To: futur.andy@googlemail.com
Cc: netdev@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH v2] bonding: ratelimit failed speed/duplex update warning
Date: Sun, 13 Aug 2017 20:02:32 -0700 (PDT) [thread overview]
Message-ID: <20170813.200232.764028072693443116.davem@davemloft.net> (raw)
In-Reply-To: <20170811223655.11446-1-futur.andy@googlemail.com>
From: Andreas Born <futur.andy@googlemail.com>
Date: Sat, 12 Aug 2017 00:36:55 +0200
> 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>
> ---
> Changes in v2:
> * swapped pr_warn_ratelimited() for net_ratelimit()
Applied and you'll be happy to know I queued this up for -stable too :)
prev parent reply other threads:[~2017-08-14 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 22:36 [PATCH v2] bonding: ratelimit failed speed/duplex update warning Andreas Born
2017-08-14 3:02 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170813.200232.764028072693443116.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=futur.andy@googlemail.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).