Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next, S23, 06/13] i40e/i40evf: tunnels can be generic
Date: Wed, 20 Jan 2016 14:39:50 -0800	[thread overview]
Message-ID: <20160120143950.00002ba0@unknown> (raw)
In-Reply-To: <569F04DF.7070102@gmail.com>

On Tue, 19 Jan 2016 19:54:07 -0800
Alexander Duyck <alexander.duyck@gmail.com> wrote:

> On 12/09/2015 03:50 PM, Hay, Joshua A wrote:
> > From: Jesse Brandeburg <jesse.brandeburg@intel.com>
> > -	if (!(tx_flags & I40E_TX_FLAGS_VXLAN_TUNNEL)) {
> > +	if ((tx_flags & I40E_TX_FLAGS_TUNNEL)) {
> >   		/* snag network header to get L4 type and address */
> >   		hdr.network = skb_network_header(skb);
> >
> 
> So this patch has a major bug right here.  Specifically it is disabling 
> ATR for everything since the logic got flipped an you are checking the 
> outer headers for tunneled frames, and the inner headers for 
> non-tunneled frames.

I've got a patch ready that fixes the "major bug" part, which appears
to be due to be a combination of several factors leading to this point
where the code was broken.  Thank you VERY much for catching this.

> There is another bug a bit further down from here where the variable 
> protocol is used which means it is outer header only and as such breaks 
> any cases where you have v4 over v6 or v6 over v4.

Since this issue was not introduced in this patch, I'm going to punt to
a separate patch to fix the "protocol".


  parent reply	other threads:[~2016-01-20 22:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 23:50 [Intel-wired-lan] [next PATCH S23 00/13] i40e/i40evf updates Joshua Hay
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 01/13] i40e: Fix Rx hash reported to the stack by our driver Joshua Hay
2015-12-16 18:31   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 02/13] i40e: remove forever unused ID Joshua Hay
2015-12-16 18:35   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 03/13] i40e: Add mac_filter_element at the end of the list instead of HEAD Joshua Hay
2015-12-16 18:37   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 04/13] i40e/i40evf: Fix RSS rx-flow-hash configuration through ethtool Joshua Hay
2016-01-13 19:25   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 05/13] i40e: Replace X722 mac check in ethtool get_settings Joshua Hay
2016-01-13 18:58   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 06/13] i40e/i40evf: tunnels can be generic Joshua Hay
2015-12-17 16:43   ` Bowers, AndrewX
2016-01-20  3:54   ` [Intel-wired-lan] [next, S23, " Alexander Duyck
2016-01-20 22:13     ` Jeff Kirsher
2016-01-20 22:39     ` Jesse Brandeburg [this message]
2016-01-20 22:44       ` Alexander Duyck
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 07/13] i40evf: allow channel bonding of VFs Joshua Hay
2015-12-17 16:49   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 08/13] i40e: define function capabilities in only one place Joshua Hay
2015-12-10 18:47   ` Jesse Brandeburg
2015-12-17 16:53   ` Bowers, AndrewX
2015-12-30 16:12     ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 09/13] i40e: Make some changes in the nvm read code Joshua Hay
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 10/13] i40evf: null out ring pointers on free Joshua Hay
2015-12-17 16:58   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 11/13] i40e: Cleanup the code with respect to restarting autoneg Joshua Hay
2015-12-17 17:00   ` Bowers, AndrewX
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 12/13] i40e: update features with right offload Joshua Hay
2015-12-10 18:46   ` Jesse Brandeburg
2015-12-09 23:50 ` [Intel-wired-lan] [next PATCH S23 13/13] i40e: bump version to 1.4.10 Joshua Hay
2015-12-17 17:09   ` Bowers, AndrewX

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=20160120143950.00002ba0@unknown \
    --to=jesse.brandeburg@intel.com \
    --cc=intel-wired-lan@osuosl.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