linux-kernel - Re: [PATCH] spi: cadence-qspi: Fix runtime PM imbalance in probe

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 for Android: free password hash cracker in your pocket

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

Message-Id: <176470771570.76978.15655951679502590234.b4-ty@kernel.org>
Date: Tue, 02 Dec 2025 20:35:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Ali Tariq <alitariq45892@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 khairul.anuar.romli@...era.com, adrianhoyin.ng@...era.com, 
 nirav.rabara@...era.com, matthew.gerlach@...era.com
Subject: Re: [PATCH] spi: cadence-qspi: Fix runtime PM imbalance in probe

On Sun, 30 Nov 2025 09:12:51 +0000, Ali Tariq wrote:
> The probe function incorrectly calls pm_runtime_put_autosuspend()
> twice in succession at the end of successful probe, dropping two
> runtime PM references while only one was acquired earlier with
> pm_runtime_get_sync(). This causes a usage count underflow:
> 
>     cadence-qspi 13010000.spi: Runtime PM usage count underflow!
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: cadence-qspi: Fix runtime PM imbalance in probe
      commit: e1f2e77624dbc35f317efd7e092aa91f7136f3f9

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