From: Chase Southwood <chase.southwood@yahoo.com>
To: Levente Kurusa <levex@linux.com>, Ian Abbott <abbotti@mev.co.uk>,
H Hartley Sweeten <hsweeten@visionengravers.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
OSUOSL Drivers <devel@driverdev.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: comedi: fix memory leak
Date: Fri, 14 Mar 2014 20:30:16 -0700 (PDT) [thread overview]
Message-ID: <1394854216.83246.YahooMailNeo@web164002.mail.gq1.yahoo.com> (raw)
In-Reply-To: <1394813775-12363-1-git-send-email-levex@linux.com>
>On Friday, March 14, 2014 11:47 AM, Levente Kurusa <levex@linux.com> wrote:
>Call kfree() on bdev. The variable is otherwise leaked.
>
>Signed-off-by: Levente Kurusa <levex@linux.com>
>---
>drivers/staging/comedi/drivers/comedi_bond.c | 1 +
>1 file changed, 1 insertion(+)
>
>diff --git a/drivers/staging/comedi/drivers/comedi_bond.c >b/drivers/staging/comedi/drivers/comedi_bond.c
>index 51a59e5..406aedb 100644
>--- a/drivers/staging/comedi/drivers/comedi_bond.c
>+++ b/drivers/staging/comedi/drivers/comedi_bond.c
>@@ -254,6 +254,7 @@ static int do_dev_config(struct comedi_device *dev, struct comedi_devconfig *it)
> if (!devs) {
> dev_err(dev->class_dev,
> "Could not allocate memory. Out of memory?\n");
>+ kfree(bdev);
> return -ENOMEM;
> }
> devpriv->devs = devs;
>--
>1.8.3.1
>
Levente,
This change has already been made in staging-next (by me, actually :) ). In
order to avoid re-doing work which has already been done, please make sure to base
all of your patches off of linux-next (or for staging, staging-next).
Thanks,
Chase
next prev parent reply other threads:[~2014-03-15 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 16:16 Levente Kurusa
2014-03-15 3:30 ` Chase Southwood [this message]
2014-03-15 6:55 ` Levente Kurusa
2014-03-15 7:21 ` Chase Southwood
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=1394854216.83246.YahooMailNeo@web164002.mail.gq1.yahoo.com \
--to=chase.southwood@yahoo.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=levex@linux.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®