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
| ||
|
Message-Id: <167492633694.2479102.1677977069431569775.b4-ty@kernel.org> Date: Sat, 28 Jan 2023 17:18:56 +0000 From: Mark Brown <broonie@...nel.org> To: Liam Girdwood <lgirdwood@...il.com>, Kees Cook <keescook@...omium.org> Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH] ASoC: kirkwood: Iterate over array indexes instead of using pointer math On Fri, 27 Jan 2023 14:41:29 -0800, Kees Cook wrote: > Walking the dram->cs array was seen as accesses beyond the first array > item by the compiler. Instead, use the array index directly. This allows > for run-time bounds checking under CONFIG_UBSAN_BOUNDS as well. Seen > with GCC 13 with -fstrict-flex-arrays: > > ../sound/soc/kirkwood/kirkwood-dma.c: In function > 'kirkwood_dma_conf_mbus_windows.constprop': > ../sound/soc/kirkwood/kirkwood-dma.c:90:24: warning: array subscript 0 is outside array bounds of 'const struct mbus_dram_window[0]' [-Warray-bounds=] > 90 | if ((cs->base & 0xffff0000) < (dma & 0xffff0000)) { > | ~~^~~~~~ > > [...] Applied to broonie/sound.git for-next Thanks! [1/1] ASoC: kirkwood: Iterate over array indexes instead of using pointer math commit: b3bcedc0402fcdc5c8624c433562d9d1882749d8 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