linux-kernel - Re: [PATCH v2] spi: microchip-core: prevent RX overflows when transmit size

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

Message-Id: <174109165049.27220.4947614753583308854.b4-ty@kernel.org>
Date: Tue, 04 Mar 2025 12:34:10 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Conor Dooley <conor.dooley@...rochip.com>
Cc: stable@...r.kernel.org, Daire McNamara <daire.mcnamara@...rochip.com>, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spi: microchip-core: prevent RX overflows when
 transmit size > FIFO size

On Mon, 03 Mar 2025 10:47:40 +0000, Conor Dooley wrote:
> When the size of a transfer exceeds the size of the FIFO (32 bytes), RX
> overflows will be generated and receive data will be corrupted and
> warnings will be produced. For example, here's an error generated by a
> transfer of 36 bytes:
> 
>   spi_master spi0: mchp_corespi_interrupt: RX OVERFLOW: rxlen: 4, txlen: 0
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: microchip-core: prevent RX overflows when transmit size > FIFO size
      commit: 91cf42c63f2d8a9c1bcdfe923218e079b32e1a69

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