From: "Stojaczyk, Dariusz" <dariusz.stojaczyk@intel.com>
To: Aaron Conole <aconole@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lipiec, Herakliusz" <herakliusz.lipiec@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"David Marchand" <dmarchan@redhat.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] ipc: unlock on failure
Date: Wed, 8 May 2019 14:24:06 +0000 [thread overview]
Message-ID: <FBE7E039FA50BF47A673AD0BD3CD56A846330607@HASMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <20190506134825.20706-1-aconole@redhat.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Aaron Conole
> Sent: Monday, May 6, 2019 3:48 PM
> To: dev@dpdk.org
> Cc: Lipiec, Herakliusz <herakliusz.lipiec@intel.com>; stable@dpdk.org;
> Burakov, Anatoly <anatoly.burakov@intel.com>; David Marchand
> <dmarchan@redhat.com>
> Subject: [dpdk-dev] [PATCH v2] ipc: unlock on failure
>
> Reported by Coverity.
>
> Fixes: a2a06860b8c4 ("ipc: fix memory leak on request failure")
> Cc: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
> Cc: stable@dpdk.org
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
> ---
Tested-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
This silences ASAN as well. :)
Thanks,
D.
next prev parent reply other threads:[~2019-05-08 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 13:11 [dpdk-stable] [PATCH] " Aaron Conole
2019-05-06 13:14 ` David Marchand
2019-05-06 13:22 ` Aaron Conole
2019-05-06 13:48 ` [dpdk-stable] [PATCH v2] " Aaron Conole
2019-05-06 14:02 ` David Marchand
2019-05-08 14:24 ` Stojaczyk, Dariusz [this message]
2019-05-09 11:50 ` Burakov, Anatoly
2019-05-09 14:31 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=FBE7E039FA50BF47A673AD0BD3CD56A846330607@HASMSX105.ger.corp.intel.com \
--to=dariusz.stojaczyk@intel.com \
--cc=aconole@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=dmarchan@redhat.com \
--cc=herakliusz.lipiec@intel.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).