linux-kernel - Re: [PATCH v2] ASoc: PCM6240: Return directly after a failed devm_kzalloc() in pcmdevice_i2c

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]

Date: Sun, 23 Jun 2024 11:50:39 +0100
From: Mark Brown <broonie@...nel.org>
To: Markus.Elfring@....de, perex@...ex.cz, tiwai@...e.com, 
 Hao Ge <hao.ge@...ux.dev>
Cc: shenghao-ding@...com, colin.i.king@...il.com, gehao618@....com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Hao Ge <gehao@...inos.cn>
Subject: Re: [PATCH v2] ASoc: PCM6240: Return directly after a failed
 devm_kzalloc() in pcmdevice_i2c_probe()

On Mon, 17 Jun 2024 10:09:54 +0800, Hao Ge wrote:
> The value “-ENOMEM” was assigned to the local variable “ret”
> in one if branch after a devm_kzalloc() call failed at the beginning.
> This error code will trigger then a pcmdevice_remove() call with a passed
> null pointer so that an undesirable dereference will be performed.
> Thus return the appropriate error code directly.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoc: PCM6240: Return directly after a failed devm_kzalloc() in pcmdevice_i2c_probe()
      commit: 3722873d49a1788d5420894d4f6f63e35f5c1f13

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