From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: LMML <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: [PATCH] [media] dib0700: Fix memory leak during initialization
Date: Thu, 08 Mar 2012 08:21:20 -0300 [thread overview]
Message-ID: <4F589630.5020008@redhat.com> (raw)
In-Reply-To: <20120212111911.32f4c390@endymion.delvare>
Hi Jean,
Em 12-02-2012 08:19, Jean Delvare escreveu:
> Reported by kmemleak.
>
> Signed-off-by: Jean Delvare <khali@linux-fr.org>
> Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
> Cc: Devin Heitmueller <dheitmueller@kernellabs.com>
> ---
> I am not familiar with the usb API, are we also supposed to call
> usb_kill_urb() in the error case maybe?
>
> drivers/media/dvb/dvb-usb/dib0700_core.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-3.3-rc3.orig/drivers/media/dvb/dvb-usb/dib0700_core.c 2012-01-20 14:06:38.000000000 +0100
> +++ linux-3.3-rc3/drivers/media/dvb/dvb-usb/dib0700_core.c 2012-02-12 00:32:19.005334036 +0100
> @@ -787,6 +787,8 @@ int dib0700_rc_setup(struct dvb_usb_devi
> if (ret)
> err("rc submit urb failed\n");
>
> + usb_free_urb(purb);
> +
> return ret;
> }
>
>
This patch doesn't sound right on my eyes, as you're freeing
an URB that you've just submitted _before_ having it handled
by the dib0700_rc_urb_completion() callback.
Btw, it seems that there's a bug at the fist if there:
static void dib0700_rc_urb_completion(struct urb *purb)
{
struct dvb_usb_device *d = purb->context;
struct dib0700_rc_response *poll_reply;
u32 uninitialized_var(keycode);
u8 toggle;
deb_info("%s()\n", __func__);
if (d == NULL)
return;
if (d->rc_dev == NULL) {
/* This will occur if disable_rc_polling=1 */
usb_free_urb(purb);
return;
}
...
it should be, instead:
if (!d || !d->rc_dev) {
/* This will occur if disable_rc_polling=1 */
usb_free_urb(purb);
return;
}
That's said, clearly there's no condition to stop the DVB IR
handling.
Probably, the right thing to do there is to add a function like:
int dib0700_disconnect(...)
{
usb_unlink_urb(urb);
usb_free_urb(urb);
dvb_usb_device_exit(...);
}
and use such function for the usb_driver disconnect handling:
static struct usb_driver dib0700_driver = {
.name = "dvb_usb_dib0700",
.probe = dib0700_probe,
.disconnect = dib0700_disconnect,
.id_table = dib0700_usb_id_table,
};
Regards,
Mauro
next prev parent reply other threads:[~2012-03-08 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 10:19 [PATCH] [media] dib0700: Fix memory leak during initialization Jean Delvare
2012-03-08 11:21 ` Mauro Carvalho Chehab [this message]
2012-03-12 10:04 ` Jean Delvare
2012-03-12 10:28 ` Mauro Carvalho Chehab
2012-03-13 17:48 ` Jean Delvare
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=4F589630.5020008@redhat.com \
--to=mchehab@redhat.com \
--cc=dheitmueller@kernellabs.com \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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.