From: Shahaf Shuler <shahafs@mellanox.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] net/mlx5: fix flow director rule deletion crash
Date: Sun, 29 Apr 2018 05:51:03 +0000 [thread overview]
Message-ID: <DB7PR05MB442601053E3F5B757917E237C3830@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180427065506.hl4bfncfyw4nyd23@laranjeiro-vm.dev.6wind.com>
Friday, April 27, 2018 9:55 AM, Nélio Laranjeiro:
> Subject: Re: [PATCH v1] net/mlx5: fix flow director rule deletion crash
>
> On Thu, Apr 26, 2018 at 06:17:46PM +0200, Adrien Mazarguil wrote:
> > Flow director rules matching traffic properties above layer 2 do not
> > target a fixed hash Rx queue (HASH_RXQ_ETH), it actually depends on
> > the highest protocol layer specified by each flow rule.
> >
> > mlx5_fdir_filter_delete() makes this wrong assumption and causes a
> > crash when attempting to destroy flow rules with L3/L4 specifications.
> >
> > Fixes: 4c3e9bcdd52e ("net/mlx5: support flow director")
> > Cc: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>
> > ---
> > drivers/net/mlx5/mlx5_flow.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/net/mlx5/mlx5_flow.c
> > b/drivers/net/mlx5/mlx5_flow.c index 8f5fcf4d6..05def2b14 100644
> > --- a/drivers/net/mlx5/mlx5_flow.c
> > +++ b/drivers/net/mlx5/mlx5_flow.c
> > @@ -3409,13 +3409,13 @@ mlx5_fdir_filter_delete(struct rte_eth_dev
> *dev,
> > if (parser.drop) {
> > struct ibv_flow_spec_action_drop *drop;
> >
> > - drop = (void
> *)((uintptr_t)parser.queue[HASH_RXQ_ETH].ibv_attr +
> > - parser.queue[HASH_RXQ_ETH].offset);
> > + drop = (void
> *)((uintptr_t)parser.queue[parser.layer].ibv_attr +
> > + parser.queue[parser.layer].offset);
> > *drop = (struct ibv_flow_spec_action_drop){
> > .type = IBV_FLOW_SPEC_ACTION_DROP,
> > .size = sizeof(struct ibv_flow_spec_action_drop),
> > };
> > - parser.queue[HASH_RXQ_ETH].ibv_attr->num_of_specs++;
> > + parser.queue[parser.layer].ibv_attr->num_of_specs++;
> > }
> > TAILQ_FOREACH(flow, &priv->flows, next) {
> > struct ibv_flow_attr *attr;
> > @@ -3426,8 +3426,8 @@ mlx5_fdir_filter_delete(struct rte_eth_dev *dev,
> > void *flow_spec;
> > unsigned int specs_n;
> >
> > - attr = parser.queue[HASH_RXQ_ETH].ibv_attr;
> > - flow_attr = flow->frxq[HASH_RXQ_ETH].ibv_attr;
> > + attr = parser.queue[parser.layer].ibv_attr;
> > + flow_attr = flow->frxq[parser.layer].ibv_attr;
> > /* Compare first the attributes. */
> > if (memcmp(attr, flow_attr, sizeof(struct ibv_flow_attr)))
> > continue;
> > --
> > 2.11.0
Applied to next-net-mlx, thanks.
>
> --
> Nélio Laranjeiro
> 6WIND
prev parent reply other threads:[~2018-04-29 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 16:17 Adrien Mazarguil
2018-04-27 6:55 ` Nélio Laranjeiro
2018-04-29 5:51 ` Shahaf Shuler [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=DB7PR05MB442601053E3F5B757917E237C3830@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).