linux-kernel - Re: [PATCH] ASoC: ops: dynamically allocate struct snd_ctl_elem

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: <174956499535.45975.12838399607440197526.b4-ty@kernel.org>
Date: Tue, 10 Jun 2025 15:16:35 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Martin Povišer <povik+lin@...ebit.org>, 
 Arnd Bergmann <arnd@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, 
 Charles Keepax <ckeepax@...nsource.cirrus.com>, 
 Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: ops: dynamically allocate struct
 snd_ctl_elem_value

On Tue, 10 Jun 2025 11:30:53 +0200, Arnd Bergmann wrote:
> This structure is really too larget to be allocated on the stack:
> 
> sound/soc/soc-ops.c:435:5: error: stack frame size (1296) exceeds limit (1280) in 'snd_soc_limit_volume' [-Werror,-Wframe-larger-than]
> 
> Change the function to dynamically allocate it instead.
> 
> There is probably a better way to do it since only two integer fields
> inside of that structure are actually used, but this is the simplest
> rework for the moment.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: ops: dynamically allocate struct snd_ctl_elem_value
      commit: 7e10d7242ea8a5947878880b912ffa5806520705

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