linux-kernel - Re: [PATCH] ASoC: imx-hdmi: add put_device() after of_find_device_by

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: <163797659312.2987942.8864055300904325575.b4-ty@kernel.org>
Date:   Sat, 27 Nov 2021 01:29:53 +0000
From:   Mark Brown <broonie@...nel.org>
To:     cgel.zte@...il.com, nicoleotsuka@...il.com
Cc:     linux-kernel@...r.kernel.org, perex@...ex.cz,
        alsa-devel@...a-project.org, kernel@...gutronix.de,
        Xiubo.Lee@...il.com, festevam@...il.com,
        Zeal Robot <zealci@....com.cn>, shawnguo@...nel.org,
        linux-arm-kernel@...ts.infradead.org, s.hauer@...gutronix.de,
        tiwai@...e.com, shengjiu.wang@...il.com,
        Ye Guojin <ye.guojin@....com.cn>, linux-imx@....com,
        lgirdwood@...il.com, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] ASoC: imx-hdmi: add put_device() after of_find_device_by_node()

On Wed, 10 Nov 2021 00:29:10 +0000, cgel.zte@...il.com wrote:
> From: Ye Guojin <ye.guojin@....com.cn>
> 
> This was found by coccicheck:
> ./sound/soc/fsl/imx-hdmi.c,209,1-7,ERROR  missing put_device; call
> of_find_device_by_node on line 119, but without a corresponding object
> release within this function.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: imx-hdmi: add put_device() after of_find_device_by_node()
      commit: f670b274f7f6f4b2722d7f08d0fddf606a727e92

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