linux-kernel - Re: [PATCH] ASoC: sma1307: Add NULL check in sma1307_setting

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: <174220666253.86423.2465322150839880396.b4-ty@kernel.org>
Date: Mon, 17 Mar 2025 10:17:42 +0000
From: Mark Brown <broonie@...nel.org>
To: kiseok.jo@...ndevice.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, Chenyuan Yang <chenyuan0y@...il.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: sma1307: Add NULL check in
 sma1307_setting_loaded()

On Mon, 10 Mar 2025 20:57:14 -0500, Chenyuan Yang wrote:
> All varibale allocated by kzalloc and devm_kzalloc could be NULL.
> Multiple pointer checks and their cleanup are added.
> 
> This issue is found by our static analysis tool
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: sma1307: Add NULL check in sma1307_setting_loaded()
      commit: 0ec6bd16705fe21d6429d6b8f7981eae2142bba8

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