linux-kernel - Re: [PATCH] ASoC: qcom: Adjust issues in case of DT error in asoc_qcom_lpass_cpu_platform

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: <171943156785.1690751.333640951846227902.b4-ty@kernel.org>
Date: Wed, 26 Jun 2024 20:52:47 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
 Aleksandr Mishin <amishin@...rgos.ru>
Cc: Banajit Goswami <bgoswami@...cinc.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>, 
 Venkata Prasad Potturu <quic_potturu@...cinc.com>, 
 alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: [PATCH] ASoC: qcom: Adjust issues in case of DT error in
 asoc_qcom_lpass_cpu_platform_probe()

On Wed, 05 Jun 2024 13:49:53 +0300, Aleksandr Mishin wrote:
> If IORESOURCE_MEM "lpass-rxtx-cdc-dma-lpm" or "lpass-va-cdc-dma-lpm"
> resources is not provided in Device Tree due to any error,
> platform_get_resource_byname() will return NULL which is later
> dereferenced. According to sound/qcom,lpass-cpu.yaml, these resources
> are provided, but DT can be broken due to any error. In such cases driver
> must be able to protect itself, since the DT is external data for the
> driver.
> Adjust this issues by adding NULL return check.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: Adjust issues in case of DT error in asoc_qcom_lpass_cpu_platform_probe()
      commit: f9f7f29f64454bb20896c7d918c3abc3a1aa487b

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