linux-kernel - Re: [PATCH] spi: core: Only check bits_per_word validity when explicitly provided

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]

Date:   Tue, 12 Apr 2022 21:43:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        paul.kocialkowski@...tlin.com
Cc:     thomas.petazzoni@...tlin.com
Subject: Re: [PATCH] spi: core: Only check bits_per_word validity when explicitly provided

On Tue, 12 Apr 2022 14:22:07 +0200, Paul Kocialkowski wrote:
> On SPI device probe, the core will call spi_setup in spi_add_device
> before the corresponding driver was probed. When this happens, the
> bits_per_word member of the device is not yet set by the driver,
> resulting in the default being set to 8 bits-per-word.
> 
> However some controllers do not support 8 bits-per-word at all, which
> results in a failure when checking the bits-per-word validity.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: core: Only check bits_per_word validity when explicitly provided
      commit: b3fe2e516741368a643d79527ebccfe557217a53

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