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: <174463899312.86688.17897930299767743328.b4-ty@kernel.org>
Date: Mon, 14 Apr 2025 14:56:33 +0100
From: Mark Brown <broonie@...nel.org>
To: shengjiu.wang@...il.com, Xiubo.Lee@...il.com, festevam@...il.com, 
 nicoleotsuka@...il.com, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de, 
 Chenyuan Yang <chenyuan0y@...il.com>
Cc: linux-sound@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, 
 imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: imx-card: Adjust over allocation of memory in
 imx_card_parse_of()

On Sun, 06 Apr 2025 16:08:54 -0500, Chenyuan Yang wrote:
> Incorrect types are used as sizeof() arguments in devm_kcalloc().
> It should be sizeof(dai_link_data) for link_data instead of
> sizeof(snd_soc_dai_link).
> 
> This 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: imx-card: Adjust over allocation of memory in imx_card_parse_of()
      commit: a9a69c3b38c89d7992fb53db4abb19104b531d32

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ