path: root/fs/locks.c
diff options
authorKees Cook <keescook@chromium.org>2020-02-19 22:22:43 -0800
committerJeff Layton <jlayton@kernel.org>2020-03-03 10:55:06 -0500
commit0a68ff5e2e7cf2263674b7f0418b31e10b2a497f (patch)
tree7ae8775298103902eb0da0f527dcf305082d162f /fs/locks.c
parentLinux 5.6-rc4 (diff)
fcntl: 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. fs/fcntl.c: In function ‘send_sigio_to_task’: fs/fcntl.c:738:20: warning: statement will never be executed [-Wswitch-unreachable] 738 | kernel_siginfo_t si; | ^~ [1] https://bugs.llvm.org/show_bug.cgi?id=44916 Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions