From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F27BD31197A for ; Thu, 27 Nov 2025 21:52:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764280353; cv=none; b=jy4+/ehiTlhWsiX5D7hgxE/5u6Ak/Ynnv3WJpUXtYI+oyY3FBuF/fskvVSE56n5GFrQ5pV3idGkyauuwNlkaljbry6UJUonHAP+y2QYPnPK7zkhLVtGh3ZBubJYrDGMbvEsqQ90MQzhYwjEYCX2tG0Etd3Ct6rI8tAAlW7efjxI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764280353; c=relaxed/simple; bh=uzwmDzRkDnw2mxAuFnL810tRe0IJUYiGjPnuK3EikTs=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=NImSjpTXdy7q3DFq72kP7WHT7RLpLNBA6bGeNPacmWADaFnVIurQeQ3UucFNZm9mpohpaV0O0Ud6Fw8Jhx2VnhZ4D7UaR3mMPlZngij+PG7oRsvod9SAtAwozZtU9aqYTMoPZP2IilZspLf21ioReK/CuGCphbbWkI6HVcR3EmM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Y3y+WZvj; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Y3y+WZvj" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 46E46C4CEF8; Thu, 27 Nov 2025 21:52:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1764280351; bh=uzwmDzRkDnw2mxAuFnL810tRe0IJUYiGjPnuK3EikTs=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=Y3y+WZvjzvXwDp4vyyUaji3KbceiJusq+AiG0tiGa7sAUA9TT9llpkbZEopDuvxQc W3C8NnH3L+jCI5V2UYk9c4bu+F0IAVRu9svHMtmGsxi1QDdZdrMC8TAeDmn0Fb/aqy +udynpwSRx2e3KQZzD9B4G4yP3xlzUCNT9nr0KiNlTa0omFxqdgGv0a59GBwmT+YQ3 0So3cDJLuthVdr7hKhCYXwMOc7aT12IWCDO3TgI5WB5c7XcaSgntQ8DzFFco1rFV3l G3KzR5PloVrNDExXNFpjp4EXb+86r+w1u/OBxdOXV8UhgqC3hDi9DQbvtZghOLhu/C qDgM00Jf3ZcIw== From: Mark Brown To: Liam Girdwood , Charles Keepax , linux-kernel@vger.kernel.org, sparkhuang Cc: weipengliang@xiaomi.com, wengjinfei@xiaomi.com, caodan1@xiaomi.com In-Reply-To: <20251127025716.5440-1-huangshaobo3@xiaomi.com> References: <20251127025716.5440-1-huangshaobo3@xiaomi.com> Subject: Re: [PATCH v2] regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex Message-Id: <176428035002.177833.18266621659221662938.b4-ty@kernel.org> Date: Thu, 27 Nov 2025 21:52:30 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-88d78 On Thu, 27 Nov 2025 10:57:16 +0800, sparkhuang wrote: > regulator_supply_alias_list was accessed without any locking in > regulator_supply_alias(), regulator_register_supply_alias(), and > regulator_unregister_supply_alias(). Concurrent registration, > unregistration and lookups can race, leading to: > > 1 use-after-free if an alias entry is removed while being read, > 2 duplicate entries when two threads register the same alias, > 3 inconsistent alias mappings observed by consumers. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex commit: 0cc15a10c3b4ab14cd71b779fd5c9ca0cb2bc30d 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