linux-kernel - Re: [PATCH v2] ASoC: amd: Adjust error handling in case of absent codec device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172010531874.64240.1946699241818022514.b4-ty@kernel.org>
Date: Thu, 04 Jul 2024 16:01:58 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>, 
 Aleksandr Mishin <amishin@...rgos.ru>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 lvc-project@...uxtesting.org
Subject: Re: [PATCH v2] ASoC: amd: Adjust error handling in case of absent
 codec device

On Wed, 03 Jul 2024 22:10:07 +0300, Aleksandr Mishin wrote:
> acpi_get_first_physical_node() can return NULL in several cases (no such
> device, ACPI table error, reference count drop to 0, etc).
> Existing check just emit error message, but doesn't perform return.
> Then this NULL pointer is passed to devm_acpi_dev_add_driver_gpios()
> where it is dereferenced.
> 
> Adjust this error handling by adding error code return.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: amd: Adjust error handling in case of absent codec device
      commit: 5080808c3339de2220c602ab7c7fa23dc6c1a5a3

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