From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 98521] New: bonding: kernel BUG at net/core/dev.c:2359 when using traceroute6
Date: Mon, 18 May 2015 10:20:09 -0700 [thread overview]
Message-ID: <20150518102009.18b9c332@urahara> (raw)
Begin forwarded message:
Date: Sun, 17 May 2015 23:16:25 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 98521] New: bonding: kernel BUG at net/core/dev.c:2359 when using traceroute6
https://bugzilla.kernel.org/show_bug.cgi?id=98521
Bug ID: 98521
Summary: bonding: kernel BUG at net/core/dev.c:2359 when using
traceroute6
Product: Networking
Version: 2.5
Kernel Version: 4.0.3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: catdog2@tuxzone.org
Regression: No
Created attachment 177171
--> https://bugzilla.kernel.org/attachment.cgi?id=177171&action=edit
Snapshot of the panic message
When i do a "traceroute6 google.com" the kernel panics with "kernel BUG at
net/core/dev.c:2359". It only seems to happen when using a bonding interface
(ethernet + wlan in active-backup mode in my case).
A snapshot of the message printed to the console is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-05-18 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 17:20 Stephen Hemminger [this message]
2015-05-18 17:53 ` Fw: [Bug 98521] New: bonding: kernel BUG at net/core/dev.c:2359 when using traceroute6 Eric Dumazet
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=20150518102009.18b9c332@urahara \
--to=stephen@networkplumber.org \
--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).