From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, danielm77@spray.se,
Jay Cliburn <jacliburn@bellsouth.net>
Subject: Re: [Bugme-new] [Bug 12087] New: [drivers/net/cxgb3/sge.c:563]: Possible memory leak: s
Date: Sat, 22 Nov 2008 21:35:32 -0800 [thread overview]
Message-ID: <20081122213532.fe01a22c.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12087-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 22 Nov 2008 21:11:51 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12087
>
> Summary: [drivers/net/cxgb3/sge.c:563]: Possible memory leak: s
> Product: Drivers
> Version: 2.5
> KernelVersion: latest git tree
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: danielm77@spray.se
>
>
> There will be a memory leak in the function alloc_ring when the parameter
> sw_size is nonzero and metadata is NULL. I don't know if that can happen.
>
> Here is the code, taken from the latest git tree.
>
> static void *alloc_ring(struct pci_dev *pdev, size_t nelem, size_t elem_size,
> size_t sw_size, dma_addr_t * phys, void *metadata)
> {
> size_t len = nelem * elem_size;
> void *s = NULL;
> void *p = dma_alloc_coherent(&pdev->dev, len, phys, GFP_KERNEL);
>
> if (!p)
> return NULL;
> if (sw_size) {
> s = kcalloc(nelem, sw_size, GFP_KERNEL);
>
> if (!s) {
> dma_free_coherent(&pdev->dev, len, p, *phys);
> return NULL;
> }
> }
> if (metadata)
> *(void **)metadata = s;
> memset(p, 0, len);
> return p;
> }
>
>
yeah, that is a bit silly-looking.
next parent reply other threads:[~2008-11-23 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12087-10286@http.bugzilla.kernel.org/>
2008-11-23 5:35 ` Andrew Morton [this message]
2008-11-23 6:03 ` [Bugme-new] [Bug 12087] New: [drivers/net/cxgb3/sge.c:563]: Possible memory leak: s Roland Dreier
2008-11-23 11:40 ` Jay Cliburn
2008-11-24 17:04 ` Divy Le Ray
2008-11-27 8:26 ` Divy Le Ray
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=20081122213532.fe01a22c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=danielm77@spray.se \
--cc=jacliburn@bellsouth.net \
--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 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.