linux-kernel - Re: [PATCH] ASoC: bcm: bcm63xx-pcm-whistler: Check return value of of_dma

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: <176477364868.48347.7323460562222971120.b4-ty@kernel.org>
Date: Wed, 03 Dec 2025 14:54:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Haotian Zhang <vulab@...as.ac.cn>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: bcm: bcm63xx-pcm-whistler: Check return value of
 of_dma_configure()

On Tue, 02 Dec 2025 18:16:42 +0800, Haotian Zhang wrote:
> bcm63xx_soc_pcm_new() does not check the return value of
> of_dma_configure(), which may fail with -EPROBE_DEFER or
> other errors, allowing PCM setup to continue with incomplete
> DMA configuration.
> 
> Add error checking for of_dma_configure() and return on failure.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: bcm: bcm63xx-pcm-whistler: Check return value of of_dma_configure()
      commit: 0ebbd45c33d0049ebf5a22c1434567f0c420b333

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