From: Takashi Iwai <tiwai@suse.de>
To: Yunseong Kim <yskelg@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
skhan@linuxfoundation.org, Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Austin Kim <austindh.kim@gmail.com>,
shjy180909@gmail.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] line6: add midibuf init failure handling in line6_init_midi()
Date: Fri, 17 May 2024 19:51:08 +0200 [thread overview]
Message-ID: <871q608gz7.wl-tiwai@suse.de> (raw)
In-Reply-To: <a258b613-3697-4f21-a8fd-20b276f63132@gmail.com>
On Fri, 17 May 2024 19:10:44 +0200,
Yunseong Kim wrote:
>
> On 5/17/24 5:32 오후, Takashi Iwai wrote:
> > The allocated object is already freed by snd_line6_midi_free() that is
> > called via rawmidi private_free at its destruction. So your change
> > would lead to a double-free.
> >
> >
> > thanks,
> >
> > Takashi
>
> Thanks for the review Takashi.
>
> I have one question:
>
> line6_midibuf_destroy() have no NULL check for the memory to free.
>
> If line6midi->midibuf_in is in this->buf = NULL from
> line6_midibuf_init() with memory allocation failed,
> won't the free(NULL) when accessed by snd_line6_midi_free() to
> line6_midibuf_destroy()?
free(NULL) is fine, it's defined to be noop.
Many codes just call free() unconditionally for that, as it reduces
the code size.
thanks,
Takashi
> In the first patch, I was making a misunderstanding
> Now that you mention it, I can see where it's freeing!
> It helped me a lot in analyzing the driver code.
>
> Please let me know if I've misunderstood anything.
>
> Warm Regards,
> Yunseong Kim
>
> >> ---
> >> sound/usb/line6/midi.c | 9 +++++++--
> >> 1 file changed, 7 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/sound/usb/line6/midi.c b/sound/usb/line6/midi.c
> >> index 0838632c788e..abcf58f46673 100644
> >> --- a/sound/usb/line6/midi.c
> >> +++ b/sound/usb/line6/midi.c
> >> @@ -283,13 +283,18 @@ int line6_init_midi(struct usb_line6 *line6)
> >>
> >> err = line6_midibuf_init(&line6midi->midibuf_in, MIDI_BUFFER_SIZE, 0);
> >> if (err < 0)
> >> - return err;
> >> + goto error;
> >>
> >> err = line6_midibuf_init(&line6midi->midibuf_out, MIDI_BUFFER_SIZE, 1);
> >> if (err < 0)
> >> - return err;
> >> + goto error;
> >>
> >> line6->line6midi = line6midi;
> >> return 0;
> >> +
> >> +error:
> >> + kfree(line6midi);
> >> + return err;
> >> +
> >> }
> >> EXPORT_SYMBOL_GPL(line6_init_midi);
> >> --
> >> 2.34.1
> >>
next prev parent reply other threads:[~2024-05-17 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 17:47 [PATCH] line6: add midibuf init failure handling in line6_init_midi() yskelg
2024-05-16 18:58 ` Bjorn Helgaas
2024-05-17 8:32 ` Takashi Iwai
2024-05-17 17:10 ` Yunseong Kim
2024-05-17 17:51 ` Takashi Iwai [this message]
2024-05-18 6:00 ` Yunseong Kim
2024-05-17 17:44 ` Bjorn Helgaas
2024-05-18 5:58 ` Yunseong Kim
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=871q608gz7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=austindh.kim@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shjy180909@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=yskelg@gmail.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