linux-kernel - Re: [PATCH] ASoC: max98373: Add checks for devm

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]

Date:   Wed, 16 Nov 2022 13:47:49 +0000
From:   Mark Brown <broonie@...nel.org>
To:     pierre-louis.bossart@...ux.intel.com,
        Jiasheng Jiang <jiasheng@...as.ac.cn>, steve@....org,
        lgirdwood@...il.com, ryan.lee.analog@...il.com, perex@...ex.cz,
        tiwai@...e.com
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: max98373: Add checks for devm_kcalloc

On Wed, 16 Nov 2022 16:25:08 +0800, Jiasheng Jiang wrote:
> As the devm_kcalloc may return NULL pointer,
> it should be better to check the return value
> in order to avoid NULL poineter dereference.
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/1] ASoC: max98373: Add checks for devm_kcalloc
      commit: 60591bbf6d5eb44f275eb733943b7757325c1b60

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