linux-kernel - Re: [PATCH] regcache: Store values more directly in maple trees

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: <172778122727.2280830.7832817289439741379.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 12:13:47 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Cc: Liam Howlett <liam.howlett@...cle.com>
Subject: Re: [PATCH] regcache: Store values more directly in maple trees

On Thu, 26 Sep 2024 12:18:41 +0200, Mark Brown wrote:
> Currently the regmap usage of the maple tree is a bit non-idomatic, rather
> than storing register values directly we allocate arrays of contiguous
> register values and store pointers to those arrays. This is all quite
> fiddly, especially around adding values (where we may need to combine a new
> allocation with adjacent ones) or dropping values (where we may have to
> keep parts of a contiguous block). One reason for doing this is that the
> maple tree wants to store pointers rather than integers, and in particular
> has some problems when we want to store 0 as a value.
> 
> [...]

Applied to

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

Thanks!

[1/1] regcache: Store values more directly in maple trees
      commit: 49a85851b14cf6630013d1b9bae2ac2345c9430b

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