linux-kernel - Re: [PATCH] regmap: kunit: Add coverage of spinlocked regmaps

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: <172529300371.119375.5933652709246901991.b4-ty@kernel.org>
Date: Mon, 02 Sep 2024 17:03:23 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: kunit: Add coverage of spinlocked regmaps

On Sun, 01 Sep 2024 12:06:14 +0100, Mark Brown wrote:
> By default regmap uses a mutex to protect the regmap but we also support
> other kinds of locking, including spinlocks, which can have an impact
> especially around allocations. Ensure that we are covering the spinlock
> case by running tests configured using fast I/O, this causes the core to
> use a spinlock instead of a mutex. Running every single test would be
> redundant but cover most of them.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: kunit: Add coverage of spinlocked regmaps
      commit: c7edb7ac8472a57e0c56a3a95796db3af98b2383

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