public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: davem@davemloft.net, Pablo Neira Ayuso <pablo@netfilter.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Jiri Pirko <jiri@mellanox.com>,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Antoine Tenart <antoine.tenart@bootlin.com>,
	thomas.petazzoni@bootlin.com
Subject: Re: [PATCH net-next] ethtool: Drop check for vlan etype and vlan tci when parsing flow_rule
Date: Wed, 29 May 2019 17:07:25 +0200	[thread overview]
Message-ID: <20190529170725.5856dd65@bootlin.com> (raw)
In-Reply-To: <20190529141044.24669-1-maxime.chevallier@bootlin.com>

On Wed, 29 May 2019 16:10:44 +0200
Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:

>When parsing an ethtool flow spec to build a flow_rule, the code checks
>if both the vlan etype and the vlan tci are specified by the user to add
>a FLOW_DISSECTOR_KEY_VLAN match.
>
>However, when the user only specified a vlan etype or a vlan tci, this
>check silently ignores these parameters.
>
>For example, the following rule :
>
>ethtool -N eth0 flow-type udp4 vlan 0x0010 action -1 loc 0
>
>will result in no error being issued, but the equivalent rule will be
>created and passed to the NIC driver :
>
>ethtool -N eth0 flow-type udp4 action -1 loc 0
>
>In the end, neither the NIC driver using the rule nor the end user have
>a way to know that these keys were dropped along the way, or that
>incorrect parameters were entered.
>
>This kind of check should be left to either the driver, or the ethtool
>flow spec layer.
>
>This commit makes so that ethtool parameters are forwarded as-is to the
>NIC driver.
>
>Since none of the users of ethtool_rx_flow_rule_create are using the
>VLAN dissector, I don't think this qualifies as a regression.
>
>Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>

I should have targeted this to -net, and provided a Fixes tag.
Let me resend that to the proper tree.

Sorry about the noise,

Maxime

      reply	other threads:[~2019-05-29 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 14:10 [PATCH net-next] ethtool: Drop check for vlan etype and vlan tci when parsing flow_rule Maxime Chevallier
2019-05-29 15:07 ` Maxime Chevallier [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=20190529170725.5856dd65@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=antoine.tenart@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=thomas.petazzoni@bootlin.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