linux-kernel - Re: [PATCH] spi: Add check for 8-bit transfer with 8 IO mode support

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: <175250960429.84734.11907940601016863610.b4-ty@kernel.org>
Date: Mon, 14 Jul 2025 17:13:24 +0100
From: Mark Brown <broonie@...nel.org>
To: Cheng Ming Lin <linchengming884@...il.com>
Cc: patrice.chotard@...s.st.com, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, alvinzhou@...c.com.tw, 
 Cheng Ming Lin <chengminglin@...c.com.tw>, stable@...r.kernel.org
Subject: Re: [PATCH] spi: Add check for 8-bit transfer with 8 IO mode
 support

On Mon, 14 Jul 2025 11:10:23 +0800, Cheng Ming Lin wrote:
> The current SPI framework does not verify if the SPI device supports
> 8 IO mode when doing an 8-bit transfer. This patch adds a check to
> ensure that if the transfer tx_nbits or rx_nbits is 8, the SPI mode must
> support 8 IO. If not, an error is returned, preventing undefined behavior.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Add check for 8-bit transfer with 8 IO mode support
      commit: 710505212e3272396394f8cf78e3ddfd05df3f22

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