linux-kernel - Re: [PATCH] ASoC: qcom: common: Fix refcount imbalance on error

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: <159846939972.39744.13708543764168639585.b4-ty@kernel.org>
Date:   Wed, 26 Aug 2020 20:16:45 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Dinghao Liu <dinghao.liu@....edu.cn>, kjlu@....edu
Cc:     Liam Girdwood <lgirdwood@...il.com>, alsa-devel@...a-project.org,
        Patrick Lai <plai@...eaurora.org>,
        linux-kernel@...r.kernel.org,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Takashi Iwai <tiwai@...e.com>,
        Banajit Goswami <bgoswami@...eaurora.org>,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Subject: Re: [PATCH] ASoC: qcom: common: Fix refcount imbalance on error

On Thu, 20 Aug 2020 12:28:27 +0800, Dinghao Liu wrote:
> for_each_child_of_node returns a node pointer np with
> refcount incremented. So when devm_kzalloc fails, a
> pairing refcount decrement is needed to keep np's
> refcount balanced.

Applied to

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

Thanks!

[1/1] ASoC: qcom: common: Fix refcount imbalance on error
      commit: c1e6414cdc371f9ed82cefebba7538499a3059f9

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