From: "David S. Miller" <davem@redhat.com>
To: David Woodhouse <dwmw2@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: Missing routes cause BUG() in icmpv6_xmit_lock().
Date: Sun, 31 Aug 2003 22:44:54 -0700 [thread overview]
Message-ID: <20030831224454.349a6a53.davem@redhat.com> (raw)
In-Reply-To: <1062341789.2785.11.camel@imladris.demon.co.uk>
On Sun, 31 Aug 2003 15:56:29 +0100
David Woodhouse <dwmw2@redhat.com> wrote:
> Attempt to ping6 the router 2002:X:Y::1 from internal host.
> Observe panic: http://www.linux.org.uk/~dwmw2/dcp_1575.jpg
The per-cpu ICMP6 socket locking is optimized assuming that
we'll never reenter the ICMP6 packet sending code on the
same processor, this link failure path is causing that to
happen.
Good thing the BUG() is there, else you'd get a lockup in this case
instead which would take us longer to hunt down :-)
I'll see what I can do about this one.
next prev parent reply other threads:[~2003-09-01 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 14:56 Missing routes cause BUG() in icmpv6_xmit_lock() David Woodhouse
2003-09-01 5:44 ` David S. Miller [this message]
2003-09-01 8:30 ` David S. Miller
2003-09-01 9:58 ` David Woodhouse
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=20030831224454.349a6a53.davem@redhat.com \
--to=davem@redhat.com \
--cc=dwmw2@redhat.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).