linux-kernel - Re: [PATCH v2] Regulator: stm32-pwr: fix of

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: <168131726636.91225.12994590690622263841.b4-ty@kernel.org>
Date:   Wed, 12 Apr 2023 17:34:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        Wei Yongjun <weiyongjun1@...wei.com>,
        YAN SHI <m202071378@...t.edu.cn>
Cc:     kernel test robot <lkp@...el.com>,
        Dongliang Mu <dzm91@...t.edu.cn>, linux-kernel@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] Regulator: stm32-pwr: fix of_iomap leak

On Wed, 12 Apr 2023 11:35:29 +0800, YAN SHI wrote:
> Smatch reports:
> drivers/regulator/stm32-pwr.c:166 stm32_pwr_regulator_probe() warn:
> 'base' from of_iomap() not released on lines: 151,166.
> 
> In stm32_pwr_regulator_probe(), base is not released
> when devm_kzalloc() fails to allocate memory or
> devm_regulator_register() fails to register a new regulator device,
> which may cause a leak.
> 
> [...]

Applied to

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

Thanks!

[1/1] Regulator: stm32-pwr: fix of_iomap leak
      commit: c4a413e56d16a2ae84e6d8992f215c4dcc7fac20

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