From: Ben Hutchings <bhutchings@solarflare.com>
To: s.poehn@stud.hs-esslingen.de
Cc: netdev@vger.kernel.org, sebastian.poehn@belden.com
Subject: Re: [PATCH] ethtool: mask out FLOW_EXT
Date: Wed, 01 Jun 2011 21:02:29 +0100 [thread overview]
Message-ID: <1306958549.2758.3.camel@bwh-desktop> (raw)
In-Reply-To: <31603.80.254.147.148.1306158835.squirrel@webmail.hs-esslingen.de>
On Mon, 2011-05-23 at 15:53 +0200, Sebastian Pöhn wrote:
> Sorry for the disclaimer the last time!
>
> The FLOW_EXT bit must be masked out. Otherwise if e.g. vlan is set a
> driver receiving the ntuple may not detect the flow_type correctly!
>
> Signed-off-by: Sebastian Poehn <sebastian.poehn@belden.com>
> ---
>
> diff --git a/ethtool.c b/ethtool.c
> index 34fe107..0b7ec05 100644
> --- a/ethtool.c
> +++ b/ethtool.c
> @@ -3134,6 +3134,9 @@ static int flow_spec_to_ntuple(struct
> ethtool_rx_flow_spec *fsp,
> (u64)ntohl(~fsp->m_ext.data[1]);
> }
> }
> +
> + /*Mask out the extended bit, because ntuple does not know it!*/
> + ntuple->flow_type &= ~FLOW_EXT;
>
> return 0;
> }
Applied, with fixes to spacing. Thanks.
In future, please ensure that your editor and mailer do *not* convert
tabs to spaces. Also put spaces between the comment delimiters and
text, consistent with the rest of the code.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2011-06-01 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 13:53 [PATCH] ethtool: mask out FLOW_EXT Sebastian Pöhn
2011-06-01 20:02 ` Ben Hutchings [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=1306958549.2758.3.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=s.poehn@stud.hs-esslingen.de \
--cc=sebastian.poehn@belden.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).