All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: netdev@vger.kernel.org
Subject: 2.6.34 + IPv6: Oops?
Date: Sat, 19 Jun 2010 19:53:52 +0200	[thread overview]
Message-ID: <20100619175352.GA8482@EIS> (raw)

Hi,

I have a NULL pointer dereference Oops here which I can reproduce, 
and I believe it's related to network / IPv6 somehow since sending a
ping from outside to the IPv6 address is what ultimately triggers it.

The box is a dedicated server with a /64 subnet assigned to it.
What I'm trying to do is tunnel part of it through IPv4 / OpenVPN.
I'm completely new to IPv6 so I'm probably doing this horribly wrong.

Unfortunately I only have a screenshot of the Oops.
I uploaded it along with other information here:

http://www.metamorpher.de/kernel/

Before the Oops I'm running a shell script (see link above) 
which among other things sets up proxy_ndp on eth0 (r8169 driver).
The Oops is triggered by sending a ping from the outside world to 
the IP which was intended to be tunneled (2a01:4f8:120:8221:ffff::2).

If you need more information, I'll try my best to provide it. 
If it's a kernel bug, I'll also be happy to test any patches.

Regards
Andreas Klauer

             reply	other threads:[~2010-06-19 18:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 17:53 Andreas Klauer [this message]
2010-06-21 15:30 ` 2.6.34 + IPv6: Oops? Andreas Klauer
2010-06-21 16:19   ` Stephen Hemminger
2010-06-21 16:26     ` Andreas Klauer
2010-06-21 16:25   ` Hagen Paul Pfeifer
2010-06-21 17:25     ` Stephen Hemminger
2010-06-21 20:04       ` Andreas Klauer
2010-06-21 21:00         ` [PATCH] ipv6: fix NULL reference in proxy neighbor discovery Stephen Hemminger
2010-06-23 14:44           ` YOSHIFUJI Hideaki
2010-06-26  4:31           ` David Miller
2010-06-22 12:29         ` 2.6.34 + IPv6: Oops? Andreas Klauer

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=20100619175352.GA8482@EIS \
    --to=andreas.klauer@metamorpher.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.