linux-kernel - Re: [PATCH] regmap: add WARN_ONCE when invalid mask is provided to regmap_field

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: <165731326159.2471691.15710953551238113950.b4-ty@kernel.org>
Date:   Fri, 08 Jul 2022 21:47:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     mranostay@...com, linux-kernel@...r.kernel.org
Cc:     nm@...com
Subject: Re: [PATCH] regmap: add WARN_ONCE when invalid mask is provided to regmap_field_init()

On Thu, 7 Jul 2022 18:31:25 -0700, Matt Ranostay wrote:
> In regmap_field_init() when a invalid mask is provided it still
> initializes with any warnings.
> 
> An example of this is when the LSB is greater than MSB a mask of zero
> is produced.
> 
> WARN_ONCE() is not ideal for this but requires less changes to core regmap
> code.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: add WARN_ONCE when invalid mask is provided to regmap_field_init()
      commit: cf39ed2e8ecddbee38e02691d6293b812e98e397

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