From: Shahaf Shuler <shahafs@mellanox.com>
To: Ori Kam <orika@mellanox.com>, Dekel Peled <dekelp@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix memory free on queue create error
Date: Sun, 26 May 2019 19:24:19 +0000 [thread overview]
Message-ID: <AM0PR0502MB3795B37636166FD9F43044D7C31C0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <AM4PR05MB3425A1CB4A4D8678B35D6889DB060@AM4PR05MB3425.eurprd05.prod.outlook.com>
Monday, May 20, 2019 8:42 PM, Ori Kam:
> Subject: RE: [dpdk-dev] [PATCH] net/mlx5: fix memory free on queue create
> error
>
>
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
> > Sent: Monday, May 20, 2019 11:07 AM
> > To: Yongseok Koh <yskoh@mellanox.com>; Shahaf Shuler
> > <shahafs@mellanox.com>
> > Cc: dev@dpdk.org; Ori Kam <orika@mellanox.com>; stable@dpdk.org
> > Subject: [dpdk-dev] [PATCH] net/mlx5: fix memory free on queue create
> > error
> >
> > In function mlx5_rxq_ibv_new(), pointer *tmpl allocation is attempted
> > at the start, but not validated or freed in case of error.
> > In function mlx5_txq_ibv_new(), pointer *txq_ibv allocation is
> > attempted at the start, but not freed in case of error.
> >
> > This patch adds pointers initialization, validation and freeing.
> >
> > Fixes: 09cb5b581762 ("net/mlx5: separate DPDK from verbs Rx queue
> > objects")
> > Fixes: faf2667fe8d5 ("net/mlx5: separate DPDK from verbs Tx queue
> > objects")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Dekel Peled <dekelp@mellanox.com>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2019-05-26 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 8:07 Dekel Peled
2019-05-20 17:41 ` Ori Kam
2019-05-26 19:24 ` 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=AM0PR0502MB3795B37636166FD9F43044D7C31C0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--cc=yskoh@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).