From: Takashi Iwai <tiwai@suse.de>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: usb-audio: Fix a potential memory leak in scarlett2_init_notify()
Date: Sun, 03 Sep 2023 18:37:19 +0200 [thread overview]
Message-ID: <87sf7vkybk.wl-tiwai@suse.de> (raw)
In-Reply-To: <8cde2320-517f-3a38-8c3f-f807791c6c52@wanadoo.fr>
On Sun, 03 Sep 2023 17:04:47 +0200,
Christophe JAILLET wrote:
>
> Le 03/09/2023 à 16:23, Takashi Iwai a écrit :
> > On Sun, 03 Sep 2023 15:06:00 +0200,
> > Christophe JAILLET wrote:
> >>
> >> If usb_alloc_coherent() or usb_urb_ep_type_check() fail, we should release
> >> the resources previously allocated.
> >
> > Those are freed in the caller side, start_input_streams() instead.
>
> Thanks for the fast review.
>
> Hmpm, If IIUC, resources allocated *before* the ending
> "ep->num_urbs++" still need to be freed here, otherwise
> free_midi_urbs() in the caller will not free them.
>
> Do you agree?
>
> If yes, I can send v2 which would look like:
> usb_alloc_urb()
> if (err)
> return -ENOMEM
>
> usb_alloc_coherent()
> if (err) {
> usb_free_urb()
> urb = NULL
> return -ENOMEM
> }
>
> usb_urb_ep_type_check()
> if (err) {
> usb_free_coherent()
> usb_free_urb()
> urb = NULL
> return -err
> }
>
> Or, if yuo prefer, with an error handling path just like below, but
> without the final free_midi_urbs() + a comment explaining that the
> caller does this part of job instead.
Indeed. The fix would be rather a oneliner like below, though:
--- a/sound/usb/midi2.c
+++ b/sound/usb/midi2.c
@@ -265,7 +265,7 @@ static void free_midi_urbs(struct snd_usb_midi2_endpoint *ep)
if (!ep)
return;
- for (i = 0; i < ep->num_urbs; ++i) {
+ for (i = 0; i < NUM_URBS; ++i) {
ctx = &ep->urbs[i];
if (!ctx->urb)
break;
That was the intended behavior of free_midi_urbs().
Takashi
next prev parent reply other threads:[~2023-09-03 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 13:06 [PATCH] ALSA: usb-audio: Fix a potential memory leak in scarlett2_init_notify() Christophe JAILLET
2023-09-03 14:23 ` Takashi Iwai
2023-09-03 15:04 ` Christophe JAILLET
2023-09-03 16:37 ` Takashi Iwai [this message]
2023-09-03 19:42 ` Christophe JAILLET
2023-09-04 14:08 ` Takashi Iwai
2023-09-05 5:39 ` Takashi Iwai
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=87sf7vkybk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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