From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <hadi@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org
Subject: Fw: New Defects reported by Coverity Scan for Linux
Date: Mon, 24 Apr 2017 16:41:27 -0700 [thread overview]
Message-ID: <20170424164127.5a2145e8@xeon-e3> (raw)
This looks like a false positive
Date: Mon, 24 Apr 2017 14:40:46 -0700
From: scan-admin@coverity.com
To: stephen@networkplumber.org
Subject: New Defects reported by Coverity Scan for Linux
1 new defect(s) introduced to Linux 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 1405487: Resource leaks (RESOURCE_LEAK)
/net/sched/act_api.c: 635 in tcf_action_init_1()
________________________________________________________________________________________________________
*** CID 1405487: Resource leaks (RESOURCE_LEAK)
/net/sched/act_api.c: 635 in tcf_action_init_1()
629 * if it exists and is only bound to in a_o->init() then
630 * ACT_P_CREATED is not returned (a zero is).
631 */
632 if (err != ACT_P_CREATED)
633 module_put(a_o->owner);
634
>>> CID 1405487: Resource leaks (RESOURCE_LEAK)
>>> Variable "cookie" going out of scope leaks the storage it points to.
635 return a;
636
637 err_mod:
638 module_put(a_o->owner);
639 err_out:
640 if (cookie) {
next reply other threads:[~2017-04-24 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 23:41 Stephen Hemminger [this message]
2017-04-25 0:09 ` Fw: New Defects reported by Coverity Scan for Linux Cong Wang
2017-04-25 0:23 ` Jamal Hadi Salim
-- strict thread matches above, loose matches on Subject: below --
2015-11-03 16:18 Stephen Hemminger
2015-11-04 1:45 ` Ying Xue
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=20170424164127.5a2145e8@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=hadi@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 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.