linux-kernel - Re: [PATCH] spi: amlogic-spifc-a1: Handle devm_pm_runtime

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: <176399835966.59465.258446054961487669.b4-ty@kernel.org>
Date: Mon, 24 Nov 2025 15:32:39 +0000
From: Mark Brown <broonie@...nel.org>
To: Haotian Zhang <vulab@...as.ac.cn>
Cc: mmkurbanov@...rdevices.ru, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: amlogic-spifc-a1: Handle devm_pm_runtime_enable()
 errors

On Mon, 24 Nov 2025 09:58:52 +0800, Haotian Zhang wrote:
> devm_pm_runtime_enable() can fail due to memory allocation. The current
> code ignores its return value, potentially causing runtime PM operations
> to fail silently after autosuspend configuration.
> 
> Check the return value of devm_pm_runtime_enable() and return on failure.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: amlogic-spifc-a1: Handle devm_pm_runtime_enable() errors
      commit: a90903c2a3c38bce475f46ea3f93dbf6a9971553

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