linux-kernel - Re: [PATCH] spi: gpio: fix const issue in spi_to_spi

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] [day] [month] [year] [list]

Message-Id: <174792108102.84499.9131453777647011628.b4-ty@kernel.org>
Date: Thu, 22 May 2025 14:38:01 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, 
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: gpio: fix const issue in spi_to_spi_gpio()

On Thu, 22 May 2025 12:57:26 +0200, Greg Kroah-Hartman wrote:
> While the struct spi_device * passed into spi_to_spi_gpio() is a const
> one, the struct spi_bitbang * that is retrieved from the controller
> field in the spi_device is NOT a const pointer, as it is coming from the
> spi_controller_get_devdata() call, and then passed to container_of()
> which would strip off the const attribute for no good reason (i.e. if a
> const pointer is passed to container_of() it still is const coming out).
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: gpio: fix const issue in spi_to_spi_gpio()
      commit: 2712a7d362904d0c4283ae91fac8cea6ecd6f9c2

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