From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net
Subject: Fw: [Bug 215950] New: bonding: kernel oops due to possible race with wifi adapters
Date: Sat, 7 May 2022 12:24:01 -0700 [thread overview]
Message-ID: <20220507122401.477d6bb5@hermes.local> (raw)
Begin forwarded message:
Date: Sat, 07 May 2022 06:24:29 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 215950] New: bonding: kernel oops due to possible race with wifi adapters
https://bugzilla.kernel.org/show_bug.cgi?id=215950
Bug ID: 215950
Summary: bonding: kernel oops due to possible race with wifi
adapters
Product: Networking
Version: 2.5
Kernel Version: 5.17.5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: smopucilowski@gmail.com
Regression: No
Created attachment 300899
--> https://bugzilla.kernel.org/attachment.cgi?id=300899&action=edit
kernel oops syslog entry
Trying to create a resilient bond with a wired and wireless interface
(https://wiki.archlinux.org/title/systemd-networkd#Bonding_a_wired_and_wireless_interface),
in which the wired interface (ethernet dongle) is spent majority unplugged.
systemd-networkd and iwd are used to manage the interfaces and wireless
connection.
Downstream bug report: https://github.com/systemd/systemd/issues/23255
Kernel oops can be triggered reliably with the systemd-networkd configuration
in the above downstream bug report. On a debug kernel, where kernel timings are
a bit slower, if oops wasn't triggered during boot when systemd-network handles
connections, then restarting iwd and systemd-networkd almost always triggers
it.
The oops appears to be a null deference in bond_slave_state:
include/net/bonding.h:242 return slave->backup;
which suggests a race condition whereby slave interfaces are brought up or down
during bond initialisation.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-05-07 19:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220507122401.477d6bb5@hermes.local \
--to=stephen@networkplumber.org \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.com \
/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