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
| ||
|
Date: Thu, 6 Feb 2020 15:28:40 -0800 From: Nick Desaulniers <ndesaulniers@...gle.com> To: caij2003@...il.com Cc: alsa-devel@...a-project.org, broonie@...nel.org, lgirdwood@...il.com, linux-kernel@...r.kernel.org, perex@...ex.cz, tiwai@...e.com, clang-built-linux@...glegroups.com Subject: RE: [PATCH] ASoC: soc-core: fix an uninitialized use > Fixed the uninitialized use of a signed integer variable ret in > soc_probe_component when all its definitions are not executed. This > caused -ftrivial-auto-var-init=pattern to initialize the variable to > repeated 0xAA (i.e. a negative value) and triggered the following code > unintentionally. > Signed-off-by: Jian Cai <caij2003@...il.com> Hi Jian, I don't quite follow; it looks like `ret` is assigned to multiple times in `soc_probe_component`. Are one of the return values of one of the functions that are called then assigned to `ret` undefined? What control flow path leaves `ret` unitialized?
Powered by blists - more mailing lists