linux-kernel - Re: [PATCH] ASoC: rockchip: Fix a reference count leak.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <159249891020.8643.15196266849523031585.b4-ty@kernel.org>
Date:   Thu, 18 Jun 2020 17:48:30 +0100
From:   Mark Brown <broonie@...nel.org>
To:     kjlu@....edu, "wu000273@....edu" <wu000273@....edu>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Sugar Zhang <sugar.zhang@...k-chips.com>,
        alsa-devel@...a-project.org, Takashi Iwai <tiwai@...e.com>,
        linux-arm-kernel@...ts.infradead.org,
        Heiko Stuebner <heiko@...ech.de>
Subject: Re: [PATCH] ASoC: rockchip: Fix a reference count leak.

On Sat, 13 Jun 2020 15:51:58 -0500, wu000273@....edu wrote:
> Calling pm_runtime_get_sync increments the counter even in case of
> failure, causing incorrect ref count if pm_runtime_put is not called in
> error handling paths. Call pm_runtime_put if pm_runtime_get_sync fails.

Applied to

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

Thanks!

[1/1] ASoC: rockchip: Fix a reference count leak.
      commit: f141a422159a199f4c8dedb7e0df55b3b2cf16cd

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