patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Xiaoyu Min <jackmin@mellanox.com>,
	stable@dpdk.org, Matan Azrad <matan@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Cc: Zengmo Gao <gaozengmo@jd.com>
Subject: Re: [dpdk-stable] [PATCH 18.11] net/mlx5: fix crash on hash Rx queue handling for drop
Date: Tue, 17 Dec 2019 14:09:07 +0000	[thread overview]
Message-ID: <0afea0a5-00eb-9045-ba22-14003328afec@redhat.com> (raw)
In-Reply-To: <1c940c177d9c4d2ccd31c9817551fa636a87f1f1.1576565806.git.jackmin@mellanox.com>

On 17/12/2019 07:26, Xiaoyu Min wrote:
> [ upstream commit 8e2f25cf3c14a9d4c4ee7cf5c6971e9fd5ad64c4 ]
> 
> When to create hrxq for the drop, it could fail on creating qp and goto
> the error handle which will release created ind_table by calling drop
> release function, which takes rte_ethdev as the only parameter and uses
> the priv->drop_queue.hrxq as input to release.
> 
> Unfortunately, at this point, the hrxq is not allocated and
> priv->drop_queue.hrxq is still NULL, which leads to a segfault.
> 
> This patch fixes the above by allocating the hrxq at first place and
> when the error happens, hrxq is released as the last one.
> 
> This patch also release other allocated resources by the correct order,
> which is missing previously.
> 
> Fixes: 78be885295b8 ("net/mlx5: handle drop queues as regular queues")
> 
> Reported-by: Zengmo Gao <gaozengmo@jd.com>
> Signed-off-by: Xiaoyu Min <jackmin@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

Thanks, applied to 18.11 branch.


      reply	other threads:[~2019-12-17 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  7:26 Xiaoyu Min
2019-12-17 14:09 ` Kevin Traynor [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=0afea0a5-00eb-9045-ba22-14003328afec@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=gaozengmo@jd.com \
    --cc=jackmin@mellanox.com \
    --cc=matan@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.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).