linux-kernel - Re: [PATCH] driver: regmap: set debugfs

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: <161531684151.49333.12973462040505596359.b4-ty@kernel.org>
Date:   Tue, 09 Mar 2021 19:07:21 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Meng.Li@...driver.com,
        gregkh@...uxfoundation.org, rafael@...nel.org
Cc:     meng.li@...driver.com
Subject: Re: [PATCH] driver: regmap: set debugfs_name to NULL after it is freed

On Fri, 26 Feb 2021 10:17:37 +0800, Meng.Li@...driver.com wrote:
> There is a upstream commit cffa4b2122f5("regmap:debugfs:
> Fix a memory leak when calling regmap_attach_dev") that
> adds a if condition when create name for debugfs_name.
> With below function invoking logical, debugfs_name is
> freed in regmap_debugfs_exit(), but it is not created again
> because of the if condition introduced by above commit.
> regmap_reinit_cache()
> 	regmap_debugfs_exit()
> 	...
> 	regmap_debugfs_init()
> So, set debugfs_name to NULL after it is freed.

Applied to

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

Thanks!

[1/1] driver: regmap: set debugfs_name to NULL after it is freed
      commit: ffe96a97642021e96ff27b29710401590ec19a5d

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