From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Duyck, Alexander H" <alexander.h.duyck@intel.com>
Cc: "edumazet@google.com" <edumazet@google.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"willemb@google.com" <willemb@google.com>,
"lkp@01.org" <lkp@01.org>, "ast@kernel.org" <ast@kernel.org>
Subject: Re: [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!
Date: Tue, 15 Nov 2016 13:56:58 +0800 [thread overview]
Message-ID: <20161115055658.GD2142@yexl-desktop> (raw)
In-Reply-To: <1479249843.681.152.camel@intel.com>
On 11/16, Duyck, Alexander H wrote:
>On Wed, 2016-11-16 at 05:20 +0800, kernel test robot wrote:
>From what I can tell it looks like the size of the frame is 0x160 hex,
>or 352. For whatever reason we are only pulling 8 bytes into the
>header which is giving us an skb->len of 352 (0x160), and a skb-
>>data_len of 344 (0x158). When we go to pull the 14 bytes for the
>Ethernet header we end up at a skb->len of 338 (0x152) which is
>resulting in the panic.
>
>The question is how are we coming up with 8 instead of 14 which is the
>lowest limit supported by eth_get_headlen? My first thought was there
>is an incorrect sizeof(eth) instead of the sizeof(*eth) somewhere in
>the code but I can't find anything like that anywhere.
>
>Is there any way you can provide me with the net/ethernet/eth.o and
>drivers/net/ethernet/igb/igb.o files? With that I can look over the
Is vmlinux ok for you? I've sent it to you separately.
Btw: I've also tried gcc-5 (Debian 5.4.1-2) 5.4.1 20160904, and the
result shows the same failures.
Thanks,
Xiaolong
next prev parent reply other threads:[~2016-11-16 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <582b7c30.nXQXP2V4/6pFiYwt%xiaolong.ye@intel.com>
2016-11-15 22:44 ` [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935! Duyck, Alexander H
2016-11-15 5:56 ` Ye Xiaolong [this message]
2016-11-22 22:04 ` Linus Torvalds
2016-11-22 22:28 ` Eric Dumazet
2016-11-22 23:30 ` Linus Torvalds
2016-11-22 22:30 ` Andre Noll
2016-11-23 6:44 ` [LKP] " Fengguang Wu
2016-11-23 7:07 ` Linus Torvalds
2016-11-23 8:36 ` Fengguang Wu
2016-11-23 8:55 ` Ye Xiaolong
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=20161115055658.GD2142@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=torvalds@linux-foundation.org \
--cc=willemb@google.com \
/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