mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sasha Levin <sashal@kernel.org>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
	Zhao Dongdong <zhaodongdong@kylinos.cn>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/core: Fix double free on stream page allocation failure
Date: Sat, 31 Oct 2026 16:38:04 +0100	[thread overview]
Message-ID: <87ecd5swwz.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261028144443.992569-1-sashal@kernel.org>

On Wed, 28 Oct 2026 15:44:43 +0100,
Sasha Levin wrote:
> 
> Since commit f16eaa38ea64 ("ALSA: hda/core: add cleanup in
> snd_hdac_bus_alloc_stream_pages()"), snd_hdac_bus_alloc_stream_pages()
> frees the BDL and position buffers it has already allocated when a
> later allocation fails.  snd_dma_free_pages() doesn't clear dmab->area,
> so the freed buffers still look allocated to
> snd_hdac_bus_free_stream_pages(), which the HDA controller drivers call
> from their destructors, and they are freed a second time when the
> device is removed.
> 
> With fault injection failing the CORB/RIRB buffer allocation of
> snd-hda-intel on a QEMU ich9-intel-hda, unbinding the device then
> crashes:
> 
>   page dumped because: VM_BUG_ON_PAGE(page_ref_count(page) == 0)
>   kernel BUG at include/linux/mm.h:1986!
>   Call Trace:
>    ___free_pages+0x9b/0xa0
>    free_pages_exact+0xa5/0xd0
>    snd_hdac_bus_free_stream_pages+0x43/0xb0 [snd_hda_core]
>    azx_free+0xb3/0x1b0 [snd_hda_intel]
>    azx_dev_free+0xd/0x20 [snd_hda_intel]
> 
> Clear the buffer pointers after freeing them in the error path.
> 
> Fixes: f16eaa38ea64 ("ALSA: hda/core: add cleanup in snd_hdac_bus_alloc_stream_pages()")
> Signed-off-by: Sasha Levin <sashal@kernel.org>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-10-31 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 14:44 Sasha Levin
2026-10-31 15:38 ` 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=87ecd5swwz.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sashal@kernel.org \
    --cc=tiwai@suse.com \
    --cc=zhaodongdong@kylinos.cn \
    /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

all inboxes | Powered by JetHome®