linux-kernel - Re: [PATCH v3] spi: fix the divide by 0 error when calculating xfer waiting 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]

Date:   Mon, 04 Jan 2021 17:41:12 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Xu Yilun <yilun.xu@...el.com>, linux-spi@...r.kernel.org
Cc:     matthew.gerlach@...ux.intel.com, lgoncalv@...hat.com,
        russell.h.weight@...el.com, hao.wu@...el.com, trix@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] spi: fix the divide by 0 error when calculating xfer waiting time

On Mon, 4 Jan 2021 09:29:09 +0800, Xu Yilun wrote:
> The xfer waiting time is the result of xfer->len / xfer->speed_hz. This
> patch makes the assumption of 100khz xfer speed if the xfer->speed_hz is
> not assigned and stays 0. This avoids the divide by 0 issue and ensures
> a reasonable tolerant waiting time.

Applied to

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

Thanks!

[1/1] spi: fix the divide by 0 error when calculating xfer waiting time
      commit: 6170d077bf92c5b3dfbe1021688d3c0404f7c9e9

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