From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Austin Schuh <austin@peloton-tech.com>, linux-can@vger.kernel.org
Subject: Re: skbuff panic
Date: Sat, 05 Jul 2014 12:40:59 +0200 [thread overview]
Message-ID: <53B7D63B.2060108@hartkopp.net> (raw)
In-Reply-To: <CANGgnMbu511sgePeix3hjitO+xEazCw1j7Ya_81SA1GsN6W+QA@mail.gmail.com>
On 04.07.2014 01:03, Austin Schuh wrote:
> I'm seeing the following panic. I've seen it on multiple kernel
> versions (3.10.24 patched, and 3.14.3).
>
> uname -a
> Linux vpc5 3.14.3-rt4abs+ #16 SMP PREEMPT RT Tue Jul 1 16:28:26 PDT
> 2014 x86_64 GNU/Linux
>
> Jul 3 12:18:28 vpc7 kernel: [ 16.691928] skbuff: skb_under_panic:
> text:ffffffff814fb64d len:-65447 put:-65463 head:ffff880407415080
> data:ffff88030742507f tail:0x58 end:0x80 dev:can0
> Jul 3 12:18:28 vpc7 kernel: [ 16.692207] ------------[ cut here ]------------
> Jul 3 12:18:28 vpc7 kernel: [ 16.692209] kernel BUG at net/core/skbuff.c:100!
(..)
> Jul 3 12:18:28 vpc7 kernel: [ 16.692330] Call Trace:
> Jul 3 12:18:28 vpc7 kernel: [ 16.692340] [<ffffffff8143e142>]
> skb_push+0x38/0x39
> Jul 3 12:18:28 vpc7 kernel: [ 16.692348] [<ffffffff814fb64d>]
> packet_rcv_spkt+0x98/0xdf
> Jul 3 12:18:28 vpc7 kernel: [ 16.692357] [<ffffffff8144b8f8>]
> __netif_receive_skb_core+0x459/0x4dc
>
> Any ideas what is causing it? The issue seems to be that the data
> pointer is less than the head pointer, from reading the code. It only
> happens right at startup.
Hi Austin,
as you are using the PF_PACKET socket here - where packet_rcv_spkt() is using
skb_push() - the things are slightly different to the PF_CAN handling.
Are these kernel panics related to the reception of CAN frames - or do they
only show up when you send CAN frames (via PF_PACKET socket)??
Can you tell something more about how you send and receive CAN frames in your
setup?
Best regards,
Oliver
next prev parent reply other threads:[~2014-07-05 10:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 23:03 skbuff panic Austin Schuh
2014-07-03 23:18 ` Austin Schuh
2014-07-05 10:40 ` Oliver Hartkopp [this message]
2014-07-05 18:38 ` Austin Schuh
2014-07-05 19:21 ` Oliver Hartkopp
2014-07-06 5:07 ` Austin Schuh
2014-07-06 12:12 ` Oliver Hartkopp
2014-07-06 16:13 ` Oliver Hartkopp
2014-07-06 19:38 ` Marc Kleine-Budde
2014-07-07 4:11 ` Austin Schuh
2014-07-10 0:07 ` Austin Schuh
2014-07-10 17:37 ` Austin Schuh
2014-07-11 13:27 ` Oliver Hartkopp
2014-07-11 14:58 ` Austin Schuh
2014-07-11 17:48 ` Marc Kleine-Budde
2015-02-19 11:48 ` Daniel Steer
2015-02-23 12:55 ` Oliver Hartkopp
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=53B7D63B.2060108@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=austin@peloton-tech.com \
--cc=linux-can@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).