From: Thomas Monjalon <thomas@monjalon.net>
To: Michael Baum <michaelba@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
stable@dpdk.org, Matan Azrad <matan@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>, Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] regex/mlx5: fix RegEx probing error flow
Date: Wed, 22 Sep 2021 21:19:34 +0200 [thread overview]
Message-ID: <4309132.uoP6ugIP2f@thomas> (raw)
In-Reply-To: <DM8PR12MB540072078E930481BF1763B0D6CD9@DM8PR12MB5400.namprd12.prod.outlook.com>
01/09/2021 10:11, Ori Kam:
> > From: Michael Baum <michaelba@nvidia.com>
> >
> > In RegEx device probing, there is register read trying after context device
> > creation.
> >
> > When the reading fails, the context device was not freed what caused a
> > memory leak.
> >
> > Free it.
> >
> > Fixes: f324162e8e77 ("regex/mlx5: support combined rule file")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Michael Baum <michaelba@nvidia.com>
>
> Thanks,
> Acked-by: Ori Kam <orika@nvidia.com>
Applied, thanks.
Title changed to:
regex/mlx5: fix leak after probing failure
prev parent reply other threads:[~2021-09-22 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 20:38 [dpdk-dev] [PATCH] regex/mlx5: fix RegEx probing error flow Michael Baum
2021-09-01 7:47 ` Matan Azrad
2021-09-01 8:11 ` Ori Kam
2021-09-22 19:19 ` Thomas Monjalon [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=4309132.uoP6ugIP2f@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.