From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: ohlavaty@redhat.com, netdev@vger.kernel.org, andrewx.bowers@intel.com
Subject: Re: [PATCH v2 net] ixgbe: fix parsing of TC actions for HW offload
Date: Thu, 31 May 2018 23:01:29 -0400 (EDT) [thread overview]
Message-ID: <20180531.230129.1440898141134890172.davem@davemloft.net> (raw)
In-Reply-To: <b67b75aeb43afd4812e378673151a629f1681eea.camel@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Thu, 31 May 2018 14:46:08 -0700
> On Thu, 2018-05-31 at 23:21 +0200, Ondřej Hlavatý wrote:
>> The previous code was optimistic, accepting the offload of whole
>> action
>> chain when there was a single known action (drop/redirect). This
>> results
>> in offloading a rule which should not be offloaded, because its
>> behavior
>> cannot be reproduced in the hardware.
>>
>> For example:
>>
>> $ tc filter add dev eno1 parent ffff: protocol ip \
>> u32 ht 800: order 1 match tcp src 42 FFFF \
>> action mirred egress mirror dev enp1s16 pipe \
>> drop
>>
>> The controller is unable to mirror the packet to a VF, but still
>> offloads the rule by dropping the packet.
>>
>> Change the approach of the function to a pessimistic one, rejecting
>> the
>> chain when an unknown action is found. This is better suited for
>> future
>> extensions.
>>
>> Note that both recognized actions always return TC_ACT_SHOT,
>> therefore
>> it is safe to ignore actions behind them.
>>
>> Signed-off-by: Ondřej Hlavatý <ohlavaty@redhat.com>
>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>
> Note- I am having our validation move to testing with GCC 8.1.1 or
> later so that we can catch warnings like Dave found in the future.
>
> Dave- Please go ahead and pick this up.
Ok, applied, thanks.
prev parent reply other threads:[~2018-06-01 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 21:21 [PATCH v2 net] ixgbe: fix parsing of TC actions for HW offload Ondřej Hlavatý
2018-05-31 21:46 ` Jeff Kirsher
2018-06-01 3:01 ` David Miller [this message]
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=20180531.230129.1440898141134890172.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrewx.bowers@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ohlavaty@redhat.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;
as well as URLs for NNTP newsgroup(s).