linux-kernel - Re: [PATCH AUTOSEL 5.10 02/25] regulator: core: avoid regulator_resolve

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: <20210203010421.GT4035784@sasha-vm>
Date:   Tue, 2 Feb 2021 20:04:21 -0500
From:   Sasha Levin <sashal@...nel.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        David Collins <collinsd@...eaurora.org>
Subject: Re: [PATCH AUTOSEL 5.10 02/25] regulator: core: avoid
 regulator_resolve_supply() race condition

On Tue, Feb 02, 2021 at 04:12:43PM +0000, Mark Brown wrote:
>On Tue, Feb 02, 2021 at 10:05:52AM -0500, Sasha Levin wrote:
>> From: David Collins <collinsd@...eaurora.org>
>>
>> [ Upstream commit eaa7995c529b54d68d97a30f6344cc6ca2f214a7 ]
>>
>> The final step in regulator_register() is to call
>> regulator_resolve_supply() for each registered regulator
>> (including the one in the process of being registered).  The
>
>This introduces a lockdep warning, there's a follow up commit if you
>want to backport it or it should be fine to just not backport either.

Okay, I'll see if it made it next week before I queue it up. Thanks!

-- 
Thanks,
Sasha