From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: kernel panic, __neigh_notify, 4.7.0-rc7, Workqueue: events_power_efficient neigh_periodic_work
Date: Mon, 25 Jul 2016 00:01:36 +0300 [thread overview]
Message-ID: <2fef7973e5b46a3707e74cc3e47cc40f@nuclearcat.com> (raw)
In-Reply-To: <fca2656caca69658277c685de29576ae@nuclearcat.com>
On 2016-07-24 21:40, nuclearcat@nuclearcat.com wrote:
> Different hardware, but same workload. Seems different bug, happened
> at least twice on this unit (both kernel panic messages here)
As additional sidenote, that might be useful (found in commits, that
proxy arp might induce this bug, such as in commit "net/neighbour: fix
crash at dumping device-agnostic proxy entries"): it is pppoe server
with proxy_arp running on it
prev parent reply other threads:[~2016-07-24 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 18:40 kernel panic, __neigh_notify, 4.7.0-rc7, Workqueue: events_power_efficient neigh_periodic_work nuclearcat
2016-07-24 21:01 ` Denys Fedoryshchenko [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=2fef7973e5b46a3707e74cc3e47cc40f@nuclearcat.com \
--to=nuclearcat@nuclearcat.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).