From: Kalle Valo <kvalo@codeaurora.org>
To: Mahesh Bandewar <maheshb@google.com>,
Andy Gospodarek <andy@greyhouse.net>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
James Feeney <james@nurealm.net>
Subject: Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers
Date: Thu, 10 Aug 2017 08:39:20 +0300 [thread overview]
Message-ID: <87shh0gewn.fsf@kamboji.qca.qualcomm.com> (raw)
Hi Mahesh and Andy,
James Feeney reported that there's a serious regression in bonding
module since v4.12, it doesn't work with wireless drivers anymore as
wireless drivers don't report the link speed via ethtool:
https://bugzilla.kernel.org/show_bug.cgi?id=196547
In the bug report it's said that this commit is the culprit:
3f3c278c94dd bonding: fix active-backup transition
Is there a fix for this or should that commit be reverted? This seems to
be a serious regression as there are multiple reports already and we
should get it fixed for v4.13, and the fix backported to v4.12 stable
release.
--
Kalle Valo
next reply other threads:[~2017-08-10 5:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 5:39 Kalle Valo [this message]
2017-08-10 12:43 ` Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers Arend van Spriel
2017-08-10 17:52 ` Andreas Born
2017-08-11 13:14 ` Kalle Valo
2017-08-12 7:35 ` Kalle Valo
2017-08-12 19:30 ` James Feeney
2017-08-13 17:42 ` Andreas Born
2017-08-16 20:44 ` James Feeney
2017-08-16 21:01 ` David Miller
2017-08-16 21:22 ` Dan Williams
2017-08-16 21:31 ` David Miller
2017-08-17 2:11 ` Dan Williams
2017-08-17 2:36 ` Ben Greear
2017-08-17 3:18 ` Dan Williams
2017-08-17 3:32 ` Ben Greear
2017-08-17 2:42 ` David Miller
2017-08-17 5:33 ` Jay Vosburgh
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=87shh0gewn.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=james@nurealm.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maheshb@google.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).