linux-kernel - Re: [PATCH] regmap: rbtree: Fix wrong register marked as in-cache when creating new node

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:   Fri, 22 Sep 2023 20:28:33 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] regmap: rbtree: Fix wrong register marked as in-cache
 when creating new node

On Fri, 22 Sep 2023 16:37:11 +0100, Richard Fitzgerald wrote:
> When regcache_rbtree_write() creates a new rbtree_node it was passing the
> wrong bit number to regcache_rbtree_set_register(). The bit number is the
> offset __in number of registers__, but in the case of creating a new block
> regcache_rbtree_write() was not dividing by the address stride to get the
> number of registers.
> 
> Fix this by dividing by map->reg_stride.
> Compare with regcache_rbtree_read() where the bit is checked.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: rbtree: Fix wrong register marked as in-cache when creating new node
      commit: 7a795ac8d49e2433e1b97caf5e99129daf8e1b08

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