linux-kernel - Re: [PATCH] regmap: Specifically test writing 0 as a value to sparse caches

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: <172778122508.2280830.5293404233468986289.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 12:13:45 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: Specifically test writing 0 as a value to
 sparse caches

On Tue, 24 Sep 2024 12:08:53 +0200, Mark Brown wrote:
> Since 0 can look a lot like a NULL pointer when used in a cache some clever
> data structures might potentially introduce bugs specific to handling it.
> Add some explicit testing of storing 0 as a value in a sparse cache, at the
> minute there are no issues and this will stop any appearing in the future.
> 
> 

Applied to

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

Thanks!

[1/1] regmap: Specifically test writing 0 as a value to sparse caches
      commit: 42afe80caff040525252af6e9601287777d144fe

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