From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 103991] New: skb legth doesn't match the sum of all the fragments length
Date: Thu, 3 Sep 2015 10:37:43 -0700 [thread overview]
Message-ID: <20150903103743.56271574@urahara> (raw)
There is really not enough information here to make a real evaluation.
kernel is old, hardware is unspecified, and the real problem is not well
identified.
Begin forwarded message:
Date: Thu, 3 Sep 2015 10:51:44 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 103991] New: skb legth doesn't match the sum of all the fragments length
https://bugzilla.kernel.org/show_bug.cgi?id=103991
Bug ID: 103991
Summary: skb legth doesn't match the sum of all the fragments
length
Product: Networking
Version: 2.5
Kernel Version: 3.13.0-62-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: tht1234@mailinator.com
Regression: No
The DUT has 2 interfaces with the same 10GB Ethernet card .
The driver and H/W support TSO at 10G speed.
IP forwarding on the DUT is enabled.
Run iperf from a system connected to one interface to a system connedted to the
second interface:
system A -------> DUT -------> system B
Watch the outgoing skbs on the DUT to system B:
On packets with nr_frags == MAX_SKB_FRAGS (17) skb_len is *NOT* equal the
some of the skb->len - skb->data_len + all of its frag->size.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-09-03 17:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150903103743.56271574@urahara \
--to=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).