From: Johannes Weiner <hannes@cmpxchg.org>
To: Takashi Iwai <tiwai@suse.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: control: fix memory leak in snd_ctl_elem_read_user()
Date: Thu, 21 Mar 2024 12:20:49 -0400 [thread overview]
Message-ID: <20240321162049.GA3379@cmpxchg.org> (raw)
In-Reply-To: <20240321161700.2926-1-hannes@cmpxchg.org>
On Thu, Mar 21, 2024 at 12:17:00PM -0400, Johannes Weiner wrote:
> With 6.9, I noticed kmalloc-2k blowing up to tens of gigabytes over
> several days. Kmemleak shows a long string of these:
>
> unreferenced object 0xffff8f1bddbce800 (size 2048):
> comm "wireplumber", pid 1058, jiffies 4294690193
> hex dump (first 32 bytes):
> 14 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................
> 4d 61 73 74 65 72 20 50 6c 61 79 62 61 63 6b 20 Master Playback
> backtrace (crc bd965d91):
> [<ffffffff85ac328b>] __kmalloc_node_track_caller+0x25b/0x370
> [<ffffffff85a79375>] memdup_user+0x25/0x80
> [<ffffffff85fa5d63>] snd_ctl_ioctl+0x753/0x880
> [<ffffffff85b18119>] __x64_sys_ioctl+0x89/0xb0
> [<ffffffff861ee190>] do_syscall_64+0x80/0x170
> [<ffffffff862000ab>] entry_SYSCALL_64_after_hwframe+0x46/0x4e
>
> When 1052d9882269 ("ALSA: control: Use automatic cleanup of kfree()")
> converted a few sites to automatic freeing, it removed the kfree from
> snd_ctl_elem_read_user() but forgot to add the __free hook.
>
> Fixes: 1052d9882269 ("ALSA: control: Use automatic cleanup of kfree()")
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Oh, I just noticed there is a pending fix at
https://lore.kernel.org/linux-sound/20240320062722.31325-1-tiwai@suse.de/
Sorry about the noise!
prev parent reply other threads:[~2024-03-21 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:17 [PATCH] ALSA: control: fix memory leak in snd_ctl_elem_read_user() Johannes Weiner
2024-03-21 16:20 ` Johannes Weiner [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=20240321162049.GA3379@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@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