linux-kernel - Re: [PATCH] regmap: dev_get_regmap

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, 03 Jul 2020 18:04:20 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Marc Kleine-Budde <mkl@...gutronix.de>
Cc:     "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH] regmap: dev_get_regmap_match(): fix string comparison

On Fri, 3 Jul 2020 12:33:15 +0200, Marc Kleine-Budde wrote:
> This function is used by dev_get_regmap() to retrieve a regmap for the
> specified device. If the device has more than one regmap, the name parameter
> can be used to specify one.
> 
> The code here uses a pointer comparison to check for equal strings. This
> however will probably always fail, as the regmap->name is allocated via
> kstrdup_const() from the regmap's config->name.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: dev_get_regmap_match(): fix string comparison
      commit: e84861fec32dee8a2e62bbaa52cded6b05a2a456

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