From: "Charles Arnold" <carnold@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: New Defects reported by Coverity Scan for XenProject
Date: Thu, 02 Apr 2015 09:43:25 -0600 [thread overview]
Message-ID: <551D0F3D02000091000F427F@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1427985164.4037.82.camel@citrix.com>
>>> On 4/2/2015 at 08:32 AM, Ian Campbell <ian.campbell@citrix.com> wrote:
> Hi Charles,
>
> I'm not sure if this is a real issue in the qdisk support for xenstat,
> but I think it may relate to the first return 0 in qmp_read which may
> not free the accumulated array.
Yes. That is a leak on the failure case.
>
> Could you take a look please?
Patch sent, Thanks
- Charles
>
> Ian.
>
> On Wed, 2015-04-01 at 05:51 -0700, scan-admin@coverity.com wrote:
>> Hi,
>>
>> Please find the latest report on new defect(s) introduced to XenProject
> found with Coverity Scan.
>>
>> 1 new defect(s) introduced to XenProject found with Coverity Scan.
>> 2 defect(s), reported by Coverity Scan earlier, were marked fixed in the
> recent build analyzed by Coverity Scan.
>>
>> New defect(s) Reported-by: Coverity Scan
>> Showing 1 of 1 defect(s)
>>
>>
>> ** CID 1292691: Resource leaks (RESOURCE_LEAK)
>> /tools/xenstat/libxenstat/src/xenstat_qmp.c: 327 in qmp_query()
>>
>>
>>
> _____________________________________________________________________________
> ___________________________
>> *** CID 1292691: Resource leaks (RESOURCE_LEAK)
>> /tools/xenstat/libxenstat/src/xenstat_qmp.c: 327 in qmp_query()
>> 321 int n;
>> 322
>> 323 n = strlen(cmd);
>> 324 if (qmp_write(qfd, cmd, n) != n)
>> 325 return NULL;
>> 326 if (!qmp_read(qfd, &qstats))
>> >>> CID 1292691: Resource leaks (RESOURCE_LEAK)
>> >>> Variable "qstats" going out of scope leaks the storage it points to.
>> 327 return NULL;
>> 328 return qstats;
>> 329 }
>> 330
>> 331 /* Returns a socket connected to the QMP socket. Returns -1 on
> failure. */
>> 332 static int qmp_connect(char *path)
>>
>>
>>
> _____________________________________________________________________________
> ___________________________
>> To view the defects in Coverity Scan visit,
> https://scan.coverity.com/projects/606?tab=overview
>>
>> To manage Coverity Scan email notifications for "ian.campbell@citrix.com",
> click
> https://scan.coverity.com/subscriptions/edit?email=ian.campbell%40citrix.com&t
> oken=1ce0fc428b9f94f66fd8d1ecf6cbb76a .
>>
next prev parent reply other threads:[~2015-04-02 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <551be9e0474d8_2970d1331454394@scan.coverity.com.mail>
2015-04-02 14:32 ` New Defects reported by Coverity Scan for XenProject Ian Campbell
2015-04-02 15:43 ` Charles Arnold [this message]
[not found] <664dc165759df_5e9362b92d249399c762@prd-scan-dashboard-0.mail>
2024-05-22 10:05 ` Jan Beulich
2024-05-22 13:49 ` Andrew Cooper
[not found] <6637576caf98c_10d9e42c57d37559ac60499@prd-scan-dashboard-0.mail>
2024-05-06 7:46 ` Jan Beulich
[not found] <6547674e54da3_1c3af2c62521719a8359bc@prd-scan-dashboard-0.mail>
2023-11-06 7:36 ` Jan Beulich
[not found] <64859cf3a1e46_712752abb10eab98834b9@prd-scan-dashboard-0.mail>
2023-06-12 10:54 ` Jan Beulich
2023-06-12 11:06 ` Andrew Cooper
[not found] <600d4d7f99bc3_241662b17c874cf6097f1@prd-scan-dashboard-0.mail>
2021-01-25 10:14 ` Jan Beulich
[not found] <5700f7b3e7d5c_3fdf4db3186252@ss1435.mail>
2016-04-04 15:07 ` Ian Jackson
[not found] <56ce8ad13abd2_bd9abd33094410@ss1435.mail>
2016-02-25 10:00 ` Ian Campbell
2016-02-25 10:06 ` George Dunlap
[not found] <E1Vgaam-0000UH-GS@build-l3.scan.coverity.com>
2013-11-13 13:51 ` Ian Campbell
2013-11-13 14:01 ` David Vrabel
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=551D0F3D02000091000F427F@prv-mh.provo.novell.com \
--to=carnold@suse.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xen.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).