From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: netdev@vger.kernel.org
Subject: ipv6: oops in datagram.c line 260
Date: Wed, 10 Dec 2014 13:43:01 +0800 [thread overview]
Message-ID: <5487DD65.60800@gtsys.com.hk> (raw)
Hi all,
We running a Dell server which crash frequently with (dell crash video
snapshot) vanilla 3.14.25
Capture viewed here: http://www.gtsys.com.hk/~chris/datagram_c_line260.png
The capture don't sadly don't show the full trace, so we lack on
information.
1st line I can see in the crash video from the idrac :
tcp_transmit_skb+0x461
RIP [<ffffffff815da587>] ipv6_local_error+0x17/0x140
The null pointer happen:
Type "apropos word" to search for commands related to "word"...
Reading symbols from net/ipv6/datagram.o...done.
(gdb) list *(ipv6_local_error+0x17)
0xae7 is in ipv6_local_error (net/ipv6/datagram.c:260).
255 struct ipv6_pinfo *np = inet6_sk(sk);
256 struct sock_exterr_skb *serr;
257 struct ipv6hdr *iph;
258 struct sk_buff *skb;
259
260 if (!np->recverr)
261 return;
262
263 skb = alloc_skb(sizeof(struct ipv6hdr), GFP_ATOMIC);
264 if (!skb)
(gdb) quit
We running a 6in4 with ipsec tunnel on the 6. I found a pull request from
Steffen Klassert
here:
http://article.gmane.org/gmane.linux.network/281469
Which might be relevant to this problem.
For time being I add a
if (np == NULL){
LIMIT_NETDEBUG(KERN_DEBUG "ipv6_pinfo is NULL\n");
return;
}
as work around to stop the server crashing
With kind regards
Chris
next reply other threads:[~2014-12-10 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 5:43 Chris Ruehl [this message]
2014-12-24 13:42 ` ipv6: oops in datagram.c line 260 Chris Ruehl
2015-01-06 16:01 ` Hannes Frederic Sowa
2015-01-07 7:22 ` Steffen Klassert
2015-01-07 10:45 ` Hannes Frederic Sowa
2015-01-07 12:26 ` Steffen Klassert
2015-01-26 8:35 ` Steffen Klassert
2015-01-27 4:20 ` Chris Ruehl
[not found] ` <54C71AFB.40300@gtsys.com.hk>
2015-01-27 11:58 ` Steffen Klassert
2015-01-28 3:50 ` Chris Ruehl
2015-02-06 7:37 ` Chris Ruehl
2015-02-10 9:57 ` Steffen Klassert
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=5487DD65.60800@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--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.