From: Thomas Monjalon <thomas@monjalon.net>
To: "Piasecki, JacekX" <jacekx.piasecki@intel.com>
Cc: dev@dpdk.org, "Jastrzebski,
MichalX K" <michalx.k.jastrzebski@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cfgfile: fix resource leak
Date: Tue, 07 Nov 2017 02:20:45 +0100 [thread overview]
Message-ID: <2164750.0ENp7ujehH@xps> (raw)
In-Reply-To: <60ABE07DBB3A454EB7FAD707B4BB158213C4B1B1@IRSMSX109.ger.corp.intel.com>
27/10/2017 17:08, Jastrzebski, MichalX K:
> >
> > Unsuccesfull memory allocation for elements inside cfgfile
> > structure could result in resource leak.
> > Fixed by pointer verification after each malloc,
> > if malloc fail - error branch is proceeded with freeing memory.
> >
> > Coverity issue: 195032
> > Fixes: d4cb8197589d ("cfgfile: support runtime modification")
> > Cc: jacekx.piasecki@intel.com
> > Cc: stable@dpdk.org
No need to Cc stable for bugs introduced in current release.
> > Signed-off-by: Jacek Piasecki <jacekx.piasecki@intel.com>
>
> Acked-by: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-11-07 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 6:21 Jacek Piasecki
2017-10-27 15:08 ` Jastrzebski, MichalX K
2017-11-07 1:20 ` 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=2164750.0ENp7ujehH@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jacekx.piasecki@intel.com \
--cc=michalx.k.jastrzebski@intel.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).