linux-kernel - Re: [PATCH v3] regmap: Call regmap_debugfs_exit() prior to

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: <164157991337.718321.10584300077901907830.b4-ty@kernel.org>
Date:   Fri, 07 Jan 2022 18:25:13 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Fabio Estevam <festevam@...il.com>
Cc:     linux-kernel@...r.kernel.org, matthias.schiffer@...tq-group.com,
        Fabio Estevam <festevam@...x.de>
Subject: Re: [PATCH v3] regmap: Call regmap_debugfs_exit() prior to _init()

On Fri, 7 Jan 2022 13:33:07 -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@...x.de>
> 
> Since commit cffa4b2122f5 ("regmap: debugfs: Fix a memory leak when
> calling regmap_attach_dev"), the following debugfs error is seen
> on i.MX boards:
> 
> debugfs: Directory 'dummy-iomuxc-gpr@...0000' with parent 'regmap' already present!
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: Call regmap_debugfs_exit() prior to _init()
      commit: 530792efa6cb86f5612ff093333fec735793b582

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