From: David Vrabel <david.vrabel@citrix.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: <konrad.wilk@oracle.com>, <boris.ostrovsky@oracle.com>,
<joe@perches.com>, <xen-devel@lists.xenproject.org>,
<linux-kernel@vger.kernel.org>, <JBeulich@suse.com>
Subject: Re: [PATCH v2] xen: fix memory leak in __xen_pcibk_add_pci_dev()
Date: Thu, 3 Apr 2014 12:55:25 +0100 [thread overview]
Message-ID: <533D4C2D.4000803@citrix.com> (raw)
In-Reply-To: <2172979.BN2CJo57Rq@daeseok-laptop.cloud.net>
On 01/04/14 11:15, Daeseok Youn wrote:
>
> It need to free dev_entry when it failed to assign to a new
> slot on the virtual PCI bus.
>
> smatch says:
> drivers/xen/xen-pciback/vpci.c:142 __xen_pcibk_add_pci_dev() warn:
> possible memory leak of 'dev_entry'
Applied to devel/for-linus-3.15.
Thanks.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: linux-kernel@vger.kernel.org, JBeulich@suse.com, joe@perches.com,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com
Subject: Re: [PATCH v2] xen: fix memory leak in __xen_pcibk_add_pci_dev()
Date: Thu, 3 Apr 2014 12:55:25 +0100 [thread overview]
Message-ID: <533D4C2D.4000803@citrix.com> (raw)
In-Reply-To: <2172979.BN2CJo57Rq@daeseok-laptop.cloud.net>
On 01/04/14 11:15, Daeseok Youn wrote:
>
> It need to free dev_entry when it failed to assign to a new
> slot on the virtual PCI bus.
>
> smatch says:
> drivers/xen/xen-pciback/vpci.c:142 __xen_pcibk_add_pci_dev() warn:
> possible memory leak of 'dev_entry'
Applied to devel/for-linus-3.15.
Thanks.
David
next prev parent reply other threads:[~2014-04-03 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 10:15 [PATCH v2] xen: fix memory leak in __xen_pcibk_add_pci_dev() Daeseok Youn
2014-04-01 10:48 ` Jan Beulich
2014-04-01 10:48 ` Jan Beulich
2014-04-03 11:55 ` David Vrabel [this message]
2014-04-03 11:55 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2014-04-01 10:15 Daeseok Youn
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=533D4C2D.4000803@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daeseok.youn@gmail.com \
--cc=joe@perches.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.