linux-kernel - Re: [PATCH v3 1/1] spi: cadence-quadspi: Implement refcount to handle unbind during busy

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: <175676563542.906617.4450367813883915988.b4-ty@kernel.org>
Date: Mon, 01 Sep 2025 23:27:15 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Matthew Gerlach <matthew.gerlach@...era.com>, 
 Niravkumar L Rabara <nirav.rabara@...era.com>, 
 Khairul Anuar Romli <khairul.anuar.romli@...era.com>
Subject: Re: [PATCH v3 1/1] spi: cadence-quadspi: Implement refcount to
 handle unbind during busy

On Tue, 26 Aug 2025 08:33:58 +0800, Khairul Anuar Romli wrote:
> driver support indirect read and indirect write operation with
> assumption no force device removal(unbind) operation. However
> force device removal(removal) is still available to root superuser.
> 
> Unbinding driver during operation causes kernel crash. This changes
> ensure driver able to handle such operation for indirect read and
> indirect write by implementing refcount to track attached devices
> to the controller and gracefully wait and until attached devices
> remove operation completed before proceed with removal operation.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: cadence-quadspi: Implement refcount to handle unbind during busy
      commit: 7446284023e8ef694fb392348185349c773eefb3

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