[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173082918893.89365.2926884723667800367.b4-ty@kernel.org>
Date: Tue, 05 Nov 2024 17:53:08 +0000
From: Mark Brown <broonie@...nel.org>
To: amelie.delaunay@...s.st.com,
Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>,
Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Olivier Moysan <olivier.moysan@...s.st.com>
Cc: Olivier Moysan <olivier.moysan@...com>, linux-sound@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ASoC: stm32: spdifrx: fix dma channel release in
stm32_spdifrx_remove
On Tue, 05 Nov 2024 15:02:42 +0100, Olivier Moysan wrote:
> In case of error when requesting ctrl_chan DMA channel, ctrl_chan is not
> null. So the release of the dma channel leads to the following issue:
> [ 4.879000] st,stm32-spdifrx 500d0000.audio-controller:
> dma_request_slave_channel error -19
> [ 4.888975] Unable to handle kernel NULL pointer dereference
> at virtual address 000000000000003d
> [...]
> [ 5.096577] Call trace:
> [ 5.099099] dma_release_channel+0x24/0x100
> [ 5.103235] stm32_spdifrx_remove+0x24/0x60 [snd_soc_stm32_spdifrx]
> [ 5.109494] stm32_spdifrx_probe+0x320/0x4c4 [snd_soc_stm32_spdifrx]
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove
commit: 9bb4af400c386374ab1047df44c508512c08c31f
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists