linux-kernel - Re: [PATCH] spi-imx: prevent overflow when estimating transfer time

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: <173220106016.54863.10499187778967280458.b4-ty@kernel.org>
Date: Thu, 21 Nov 2024 14:57:40 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Antonio Quartulli <antonio@...delbit.com>
Cc: Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, 
 Pengutronix Kernel Team <kernel@...gutronix.de>, 
 Fabio Estevam <festevam@...il.com>, imx@...ts.linux.dev, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi-imx: prevent overflow when estimating transfer
 time

On Fri, 15 Nov 2024 23:02:02 +0100, Antonio Quartulli wrote:
> The words delay is computed by multiplying two unsigned ints
> and by adding up the result to a u64 variable.
> 
> The multiplication, however, is performed with 32bit math
> thus losing data when the actual result is larger than UINT32_MAX.
> 
> Fix the operation by casting the first operand to u64, thus forcing
> the multiplication to be performed with 64bit math.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi-imx: prevent overflow when estimating transfer time
      commit: 9e141955ede223d82251a59644ff9448a5aba580

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