linux-kernel - Re: [PATCH 0/3] regmap: Add KUnit tests for read/write checking

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: <168676416227.217135.12550330638689341135.b4-ty@kernel.org>
Date:   Wed, 14 Jun 2023 18:36:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 0/3] regmap: Add KUnit tests for read/write checking

On Tue, 13 Jun 2023 21:17:41 +0100, Mark Brown wrote:
> Since Takashi found an issue with maple tree syncing registers it
> shouldn't do add some test cases that catch that case and some more
> potential issues, ideally we'd run through the combination of
> readability with all possible I/O calls but that's lifting for another
> day.  We did find one issue with missing readability checks which will
> be fixed separately.
> 
> [...]

Applied to

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

Thanks!

[1/3] regmap: Add test that writes to write only registers are prevented
      commit: 180033061e203a7c5510e7c38bccd885657de517
[2/3] regmap: Add a test case for write only registers
      commit: a07bff4054c9e2b3a5c5790312a4a45aaeca7afe
[3/3] regmap: Add test to make sure we don't sync to read only registers
      commit: 357a1ebd0c012f5421252547ebf4ee619b45733d

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