[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174560282390.225473.13689303737740038724.b4-ty@kernel.org>
Date: Fri, 25 Apr 2025 18:40:23 +0100
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org,
Venkata Prasad Potturu <venkataprasad.potturu@....com>
Cc: Vijendar.Mukunda@....com, Basavaraj.Hiregoudar@....com,
Sunil-kumar.Dommati@....com, syed.sabakareem@....com,
mario.limonciello@....com, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Uwe Kleine-König <u.kleine-koenig@...libre.com>,
Greg KH <gregkh@...uxfoundation.org>, Peter Zijlstra <peterz@...radead.org>,
"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." <linux-sound@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] ASoC: amd: acp: Fix NULL pointer deref on acp
resume path
On Fri, 25 Apr 2025 11:31:39 +0530, Venkata Prasad Potturu wrote:
> update chip data using dev_get_drvdata(dev->parent) instead of
> dev_get_platdata(dev).
>
> BUG: kernel NULL pointer dereference, address: 0000000000000010
> Call Trace:
> <TASK>
> ? __pfx_platform_pm_resume+0x10/0x10
> platform_pm_resume+0x28/0x60
> dpm_run_callback+0x51/0x1a0
> device_resume+0x1a6/0x2b0
> dpm_resume+0x168/0x230
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: amd: acp: Fix NULL pointer deref on acp resume path
commit: ba85883d160515129b58873f74376a89faf21c7c
[2/3] ASoC: amd: acp: Fix NULL pointer deref in acp_i2s_set_tdm_slot
commit: 6d9b64156d849e358cb49b6b899fb0b7d262bda8
[3/3] ASoC: amd: acp: Fix devm_snd_soc_register_card(acp-pdm-mach) failure
commit: 138e6da0392ed067d0db7b5b5b4582c3668cfcf9
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