Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: liam.girdwood@wolfsonmicro.com, alsa-devel@alsa-project.org,
	nico@cam.org, tiwai@suse.com
Subject: Re: [PATCH] ALSA: ac97: fix possible memory leak in snd_ac97_dev_register()
Date: Thu, 20 Oct 2022 14:20:09 +0200	[thread overview]
Message-ID: <8735biadqe.wl-tiwai@suse.de> (raw)
In-Reply-To: <20221019093025.1179475-1-yangyingliang@huawei.com>

On Wed, 19 Oct 2022 11:30:25 +0200,
Yang Yingliang wrote:
> 
> If device_register() fails in snd_ac97_dev_register(), it should
> call put_device() to give up reference, or the name allocated in
> dev_set_name() is leaked.
> 
> Fixes: 0ca06a00e206 ("[ALSA] AC97 bus interface for ad-hoc drivers")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>

Thanks, applied.


Takashi

      reply	other threads:[~2022-10-20 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  9:30 [PATCH] ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() Yang Yingliang
2022-10-20 12:20 ` Takashi Iwai [this message]

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=8735biadqe.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.girdwood@wolfsonmicro.com \
    --cc=nico@cam.org \
    --cc=tiwai@suse.com \
    --cc=yangyingliang@huawei.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