aboutsummaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2020-02-19 22:23:18 -0800
committerBoris Ostrovsky <boris.ostrovsky@oracle.com>2020-02-20 10:16:40 -0600
commit9038ec99ceb94fb8d93ade5e236b2928f0792c7c (patch)
tree1bd056a3cba73a2bf1455a2c13330ea26f810b1a /drivers
parentxen/blkback: Consistently insert one empty line between functions (diff)
downloadlinux-dev-9038ec99ceb94fb8d93ade5e236b2928f0792c7c.tar.xz
linux-dev-9038ec99ceb94fb8d93ade5e236b2928f0792c7c.zip
x86/xen: Distribute switch variables for initialization
Variables declared in a switch statement before any case statements cannot be automatically initialized with compiler instrumentation (as they are not part of any execution flow). With GCC's proposed automatic stack variable initialization feature, this triggers a warning (and they don't get initialized). Clang's automatic stack variable initialization (via CONFIG_INIT_STACK_ALL=y) doesn't throw a warning, but it also doesn't initialize such variables[1]. Note that these warnings (or silent skipping) happen before the dead-store elimination optimization phase, so even when the automatic initializations are later elided in favor of direct initializations, the warnings remain. To avoid these problems, move such variables into the "case" where they're used or lift them up into the main function body. arch/x86/xen/enlighten_pv.c: In function ‘xen_write_msr_safe’: arch/x86/xen/enlighten_pv.c:904:12: warning: statement will never be executed [-Wswitch-unreachable] 904 | unsigned which; | ^~~~~ [1] https://bugs.llvm.org/show_bug.cgi?id=44916 Signed-off-by: Kees Cook <keescook@chromium.org> Link: https://lore.kernel.org/r/20200220062318.69299-1-keescook@chromium.org Reviewed-by: Juergen Gross <jgross@suse.com> [boris: made @which an 'unsigned int'] Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions