From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Subject: 3.3-rc snmp6 panic
Date: Thu, 15 Mar 2012 01:25:06 -0400 [thread overview]
Message-ID: <20120315052506.GA5974@redhat.com> (raw)
I've been seeing an occasional panic when I shut down my router
since I put 3.3 on there. It happens about once a week, always during
shutdown. It wedges before I can get a good capture of the trace.
This is the best I've captured so far.. https://twitpic.com/8wh5l5
(apologies in advance for blurriness)
>From comparing the Code: line, and the objdump output, the code it's
choking on in mld_sendpack seems to be a skb_dst macro in the NF_HOOK..
err = NF_HOOK(NFPROTO_IPV6, NF_INET_LOCAL_OUT, skb, NULL, skb->dev,
2dd9: 4c 8b 43 20 mov 0x20(%rbx),%r8
2ddd: e9 00 00 00 00 jmpq 2de2 <mld_sendpack+0x1b2>
static inline struct dst_entry *skb_dst(const struct sk_buff *skb)
{
/* If refdst was not refcounted, check we still are in a
* rcu_read_lock section
*/
WARN_ON((skb->_skb_refdst & SKB_DST_NOREF) &&
2de2: 48 8b 43 58 mov 0x58(%rbx),%rax
2de6: a8 01 test $0x1,%al
2de8: 0f 85 d2 01 00 00 jne 2fc0 <mld_sendpack+0x390>
!rcu_read_lock_held() &&
!rcu_read_lock_bh_held());
return (struct dst_entry *)(skb->_skb_refdst & SKB_DST_PTRMASK);
2dee: 48 83 e0 fe and $0xfffffffffffffffe,%rax
2df2: 48 89 df mov %rbx,%rdi
2df5: ff 50 58 callq *0x58(%rax) <----- BOOM
This machine is running an snmpd, for my mrtg setup, so the teardown of that
service is probably what's triggering it. But I can start/stop it in a loop
as much as I want without it happening, so maybe the kernel needs to accumulate
some state from it for a while first ?
Anyone have any ideas what's happening here ?
Dave
next reply other threads:[~2012-03-15 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 5:25 Dave Jones [this message]
2012-03-15 6:56 ` 3.3-rc snmp6 panic Eric Dumazet
2012-03-15 7:13 ` Eric Dumazet
2012-03-16 8:53 ` David Miller
2012-03-15 14:42 ` Dave Jones
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=20120315052506.GA5974@redhat.com \
--to=davej@redhat.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 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.