All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: syzbot+08a7d8b51ea048a74ffb@syzkaller.appspotmail.com,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	tiwai@suse.com
Subject: Re: [PATCH] ALSA: control led: fix memory leak in snd_ctl_led_register
Date: Fri, 28 May 2021 16:33:09 +0300	[thread overview]
Message-ID: <20210528133309.GR24442@kadam> (raw)
In-Reply-To: <20210528131757.2269989-1-mudongliangabcd@gmail.com>

On Fri, May 28, 2021 at 09:17:57PM +0800, Dongliang Mu wrote:
> The snd_ctl_led_sysfs_add and snd_ctl_led_sysfs_remove should contain
> the refcount operations in pair. However, snd_ctl_led_sysfs_remove fails
> to decrease the refcount to zero, which causes device_release never to
> be invoked. This leads to memory leak to some resources, like struct
> device_private.
> 
> Fix this by calling put_device at the end of snd_ctl_led_sysfs_remove
> 
> Reported-by: syzbot+08a7d8b51ea048a74ffb@syzkaller.appspotmail.com
> Fixes: a135dfb5de1 ("ALSA: led control - add sysfs kcontrol LED marking layer")
> Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
> ---
>  sound/core/control_led.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/sound/core/control_led.c b/sound/core/control_led.c
> index 25f57c14f294..fff2688b5019 100644
> --- a/sound/core/control_led.c
> +++ b/sound/core/control_led.c
> @@ -371,6 +371,10 @@ static void snd_ctl_led_disconnect(struct snd_card *card)
>  	snd_ctl_led_refresh();
>  }
>  
> +static void snd_ctl_led_release(struct device *dev)
> +{
> +}

Whatever you're trying to do, adding a dummy function is never the
answer.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org,
	syzbot+08a7d8b51ea048a74ffb@syzkaller.appspotmail.com
Subject: Re: [PATCH] ALSA: control led: fix memory leak in snd_ctl_led_register
Date: Fri, 28 May 2021 16:33:09 +0300	[thread overview]
Message-ID: <20210528133309.GR24442@kadam> (raw)
In-Reply-To: <20210528131757.2269989-1-mudongliangabcd@gmail.com>

On Fri, May 28, 2021 at 09:17:57PM +0800, Dongliang Mu wrote:
> The snd_ctl_led_sysfs_add and snd_ctl_led_sysfs_remove should contain
> the refcount operations in pair. However, snd_ctl_led_sysfs_remove fails
> to decrease the refcount to zero, which causes device_release never to
> be invoked. This leads to memory leak to some resources, like struct
> device_private.
> 
> Fix this by calling put_device at the end of snd_ctl_led_sysfs_remove
> 
> Reported-by: syzbot+08a7d8b51ea048a74ffb@syzkaller.appspotmail.com
> Fixes: a135dfb5de1 ("ALSA: led control - add sysfs kcontrol LED marking layer")
> Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
> ---
>  sound/core/control_led.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/sound/core/control_led.c b/sound/core/control_led.c
> index 25f57c14f294..fff2688b5019 100644
> --- a/sound/core/control_led.c
> +++ b/sound/core/control_led.c
> @@ -371,6 +371,10 @@ static void snd_ctl_led_disconnect(struct snd_card *card)
>  	snd_ctl_led_refresh();
>  }
>  
> +static void snd_ctl_led_release(struct device *dev)
> +{
> +}

Whatever you're trying to do, adding a dummy function is never the
answer.

regards,
dan carpenter


  reply	other threads:[~2021-05-28 13:34 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 13:17 [PATCH] ALSA: control led: fix memory leak in snd_ctl_led_register Dongliang Mu
2021-05-28 13:33 ` Dan Carpenter [this message]
2021-05-28 13:33   ` Dan Carpenter
2021-05-28 13:50   ` Dongliang Mu
2021-05-28 13:50     ` Dongliang Mu
2021-05-28 14:05     ` Dan Carpenter
2021-05-28 14:05       ` Dan Carpenter
2021-05-28 21:35       ` 慕冬亮
2021-05-28 21:35         ` 慕冬亮
2021-05-31  3:03         ` Dongliang Mu
2021-05-31  3:03           ` Dongliang Mu
2021-05-31  4:40           ` Dan Carpenter
2021-05-31  4:40             ` Dan Carpenter
2021-05-31  6:20             ` Dongliang Mu
2021-05-31  6:20               ` Dongliang Mu
2021-05-31  7:03               ` Dan Carpenter
2021-05-31  7:03                 ` Dan Carpenter
2021-05-31  7:34                 ` Dongliang Mu
2021-05-31  7:34                   ` Dongliang Mu
2021-05-31  8:08                   ` Dongliang Mu
2021-05-31  8:08                     ` Dongliang Mu
2021-05-31  8:46                     ` Dan Carpenter
2021-05-31  8:46                       ` Dan Carpenter
2021-05-31  9:10                       ` Dongliang Mu
2021-05-31  9:10                         ` Dongliang Mu
2021-05-31  9:38                         ` Dan Carpenter
2021-05-31  9:38                           ` Dan Carpenter
2021-05-31 10:35                           ` Dongliang Mu
2021-05-31 10:35                             ` Dongliang Mu
2021-05-31 10:43                             ` Dan Carpenter
2021-05-31 10:43                               ` Dan Carpenter
2021-05-31 10:59                               ` Dongliang Mu
2021-05-31 10:59                                 ` Dongliang Mu
2021-05-31  8:12                   ` Dan Carpenter
2021-05-31  8:12                     ` Dan Carpenter
2021-05-31  4:36         ` Dan Carpenter
2021-05-31  4:36           ` Dan Carpenter
2021-05-31 11:01 ` Dan Carpenter
2021-05-31 11:01   ` Dan Carpenter
2021-05-31 11:07   ` Dan Carpenter
2021-05-31 11:07     ` Dan Carpenter
2021-05-31 11:11     ` Dongliang Mu
2021-05-31 11:11       ` Dongliang Mu
2021-06-01 13:17   ` Dongliang Mu
2021-06-01 13:17     ` Dongliang Mu
2021-06-01 13:46     ` Dan Carpenter
2021-06-01 13:46       ` Dan Carpenter
2021-06-01 14:19       ` Dongliang Mu
2021-06-01 14:19         ` Dongliang Mu
2021-06-01 14:43         ` Dan Carpenter
2021-06-01 14:43           ` Dan Carpenter
2021-06-01 15:52           ` Dongliang Mu
2021-06-01 15:52             ` Dongliang Mu

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=20210528133309.GR24442@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mudongliangabcd@gmail.com \
    --cc=syzbot+08a7d8b51ea048a74ffb@syzkaller.appspotmail.com \
    --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 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.