From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: "Nelson, Shannon" <shannon.nelson@intel.com>
Cc: Tom Herbert <tom@herbertland.com>, Jesse Gross <jesse@nicira.com>,
"Jiri Benc" <jbenc@redhat.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
jesse.brandeburg@intel.com
Subject: Re: WARN trace - skb_warn_bad_offload - vxlan - large udp packet - udp checksum disabled
Date: Wed, 6 Jan 2016 18:23:54 -0800 [thread overview]
Message-ID: <20160106182354.000044e9@unknown> (raw)
In-Reply-To: <FC41C24E35F18A40888AACA1A36F3E418AFD00B5@fmsmsx115.amr.corp.intel.com>
On Tue, 15 Dec 2015 01:35:27 +0000
"Nelson, Shannon" <shannon.nelson@intel.com> wrote:
> Using a slightly modified version of udpspam (see diff below - hopefully
> not mangled by corporate email servers), where I set the SO_NO_CHECK
> socket option and can specify a large buffer size, I can reliably get
> the following WARN trace. I have reproduced this on both ixgbe and
> i40e drivers using "udpspam-no-check <target-ip> 6000".
>
> It looks to me like this is in the Tx path before we get to the actual
> NIC drivers, but I may be wrong.
>
>
> [ 1757.644324] ------------[ cut here ]------------
> [ 1757.644333] WARNING: CPU: 22 PID: 5537 at net/core/dev.c:2423 skb_warn_bad_offload+0x104/0x111()
Was anyone able to take a look at this? There is a pretty clear
reproducer in the original mail.
I know SO_NO_CHECK is a lightly used option, but it does exist and we
found a userspace program that tries to use it.
next prev parent reply other threads:[~2016-01-07 2:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 1:35 WARN trace - skb_warn_bad_offload - vxlan - large udp packet - udp checksum disabled Nelson, Shannon
2016-01-07 2:23 ` Jesse Brandeburg [this message]
2016-01-07 2:36 ` Hannes Frederic Sowa
2016-01-07 6:46 ` Michal Kubecek
2016-01-07 7:27 ` Michal Kubecek
2016-01-08 19:14 ` Michal Kubecek
2016-01-09 0:50 ` Nelson, Shannon
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=20160106182354.000044e9@unknown \
--to=jesse.brandeburg@intel.com \
--cc=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@intel.com \
--cc=tom@herbertland.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 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.