From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Oostdyk <daveo@ll.mit.edu>
Cc: netdev@vger.kernel.org, macro@linux-mips.org
Subject: Re: defxx: skb_push() failing?
Date: Tue, 26 Mar 2013 08:15:00 -0700 [thread overview]
Message-ID: <1364310900.1716.21.camel@edumazet-glaptop> (raw)
In-Reply-To: <5151B0CE.5000000@ll.mit.edu>
On Tue, 2013-03-26 at 10:29 -0400, David Oostdyk wrote:
> Hello,
>
> In dfx_xmt_queue_pkt() in defxx.c, there is a skb_push(3) call which
> makes room for 3 packet request header bytes. There is some discussion
> in the driver explaining why those three bytes will be available. I
> have an old FDDI card that I'm trying to bring up:
>
> 05:05.0 FDDI network controller: Digital Equipment Corporation
> PCI-to-PDQ Interface Chip [PFI] (rev 02)
>
> Most skbuffs that come through dfx_xmit_queue_pkt() have 11 bytes
> between skb->head and skb->data. On the other hand, at almost exactly
> 60-second intervals, an skb arrives that has zero bytes between
> skb->head and skb->data. This normally causes a kernel panic, and for
> the time I just skip over such skb's.
>
> Does anyone have advice on where I should start digging to find the
> cause of this?
>
Have you read comments in defxx.c file around line 151 ?
If one skb arrives with not enough headroom, you could add a
WARN_ON_ONCE(skb_headroom(skb) < 3);
and report stack trace so that we can identify and fix the caller.
next prev parent reply other threads:[~2013-03-26 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:29 defxx: skb_push() failing? David Oostdyk
2013-03-26 15:15 ` Eric Dumazet [this message]
2013-03-26 16:03 ` David Oostdyk
2013-03-26 16:30 ` Eric Dumazet
2013-03-26 18:45 ` David Oostdyk
2013-03-26 19:00 ` Maciej W. Rozycki
2013-03-28 4:11 ` David Oostdyk
2013-03-28 4:28 ` [PATCH] aoe: reserve enough headroom on skbs Eric Dumazet
2013-03-28 18:30 ` David Miller
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=1364310900.1716.21.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=daveo@ll.mit.edu \
--cc=macro@linux-mips.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox