linux-kernel - Re: [PATCH] regulator: core: Prevent integer underflow

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:   Fri, 09 Sep 2022 23:57:00 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Patrick Rudolph <patrick.rudolph@...ements.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: core: Prevent integer underflow

On Fri, 9 Sep 2022 14:59:53 +0200, Patrick Rudolph wrote:
> By using a ratio of delay to poll_enabled_time that is not integer
> time_remaining underflows and does not exit the loop as expected.
> As delay could be derived from DT and poll_enabled_time is defined
> in the driver this can easily happen.
> 
> Use a signed iterator to make sure that the loop exits once
> the remaining time is negative.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: Prevent integer underflow
      commit: 8d8e16592022c9650df8aedfe6552ed478d7135b

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