linux-kernel - Re: [PATCH] regulator: core: Fix off_on

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: <161920103666.15429.14029390761495428957.b4-ty@kernel.org>
Date:   Fri, 23 Apr 2021 19:06:16 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        kernel@...s.com, guodong.xu@...aro.org
Subject: Re: [PATCH] regulator: core: Fix off_on_delay handling

On Fri, 23 Apr 2021 13:45:24 +0200, Vincent Whitchurch wrote:
> The jiffies-based off_on_delay implementation has a couple of problems
> that cause it to sometimes not actually delay for the required time:
> 
>  (1) If, for example, the off_on_delay time is equivalent to one jiffy,
>      and the ->last_off_jiffy is set just before a new jiffy starts,
>      then _regulator_do_enable() does not wait at all since it checks
>      using time_before().
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: Fix off_on_delay handling
      commit: a8ce7bd89689997537dd22dcbced46cf23dc19da

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