linux-kernel - Re: [PATCH 0/2] regmap: kunit: Add test for cache sync interaction with range selectors

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]

Date:   Thu, 26 Oct 2023 19:16:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Hector Martin <marcan@...can.st>, linux-kernel@...r.kernel.org,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 0/2] regmap: kunit: Add test for cache sync interaction
 with range selectors

On Mon, 23 Oct 2023 18:19:10 +0100, Mark Brown wrote:
> Add a test for a bug reported by Hector Martin, plus a fix for a thinko
> in the tests that I spotted while adding that test case.  I've not
> included a fix since I believe Hector either has or is working on
> something and I don't want to invalidate his work.
> 
> Hector also reports that there is a similar interaction around cache
> initialisation from device defaults.
> 
> [...]

Applied to

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

Thanks!

[1/2] regmap: kunit: Fix marking of the range window as volatile
      commit: fabe32cc1eca7857837abcb56b242bc4845b7067
[2/2] regmap: kunit: Add test for cache sync interaction with ranges
      commit: 6a2e332c2cbddd17d7dcb8f334953593f1324c8e

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