Netdev List
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: "Nelson, Shannon" <shannon.nelson@intel.com>,
	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>
Subject: Re: WARN trace - skb_warn_bad_offload - vxlan - large udp packet - udp checksum disabled
Date: Thu, 7 Jan 2016 03:36:27 +0100	[thread overview]
Message-ID: <568DCF2B.2090502@stressinduktion.org> (raw)
In-Reply-To: <FC41C24E35F18A40888AACA1A36F3E418AFD00B5@fmsmsx115.amr.corp.intel.com>

On 15.12.2015 02:35, Nelson, Shannon 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.

Does UFO offloading on the tunnel interface fix this error?

ethtool -K vxlan ufo off

If yes we can't feed SO_NO_CHECK udp packets into UFO as gso/ufo 
requires CHECKSUM_PARTIAL (or add some more logic into the skb or query 
socket status from skb_gso_segment).

Thanks,
Hannes

  parent reply	other threads:[~2016-01-07  2:36 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
2016-01-07  2:36 ` Hannes Frederic Sowa [this message]
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=568DCF2B.2090502@stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox