From: Jeff Garzik <jeff@garzik.org>
To: Florin Malita <fmalita@gmail.com>
Cc: baum@tehutinetworks.net, andy@greyhouse.net,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] tehuti: possible leak in bdx_probe
Date: Mon, 15 Oct 2007 14:34:00 -0400 [thread overview]
Message-ID: <4713B298.2030709@garzik.org> (raw)
In-Reply-To: <4710FA6A.2070902@gmail.com>
Florin Malita wrote:
> If pci_enable_device fails, bdx_probe returns without freeing the
> allocated pci_nic structure.
>
> Coverity CID 1908.
>
> Signed-off-by: Florin Malita <fmalita@gmail.com>
> ---
>
> drivers/net/tehuti.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
applied
prev parent reply other threads:[~2007-10-15 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 17:03 [PATCH] tehuti: possible leak in bdx_probe Florin Malita
2007-10-14 8:30 ` Alexander Indenbaum
2007-10-15 13:33 ` Andy Gospodarek
2007-10-15 18:34 ` Jeff Garzik [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=4713B298.2030709@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=andy@greyhouse.net \
--cc=baum@tehutinetworks.net \
--cc=fmalita@gmail.com \
--cc=netdev@vger.kernel.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).