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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 19 Sep 2014 08:29:35 -0700 From: Jeff Kirsher <jeffrey.t.kirsher@...el.com> To: sparse@...isli.org Cc: Mark Rustad <mark.d.rustad@...el.com>, linux-sparse@...r.kernel.org, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, <x86@...nel.org>, Brian Norris <computersforpeace@...il.com>, Jeff Kirsher <jeffrey.t.kirsher@...el.com> Subject: [PATCH 2/7] x86: Silence initializer-overrides warnings From: Mark Rustad <mark.d.rustad@...el.com> Since the syscall table intentionally uses override initialization, simply silence those warnings. CC: Thomas Gleixner <tglx@...utronix.de> CC: Ingo Molnar <mingo@...hat.com> CC: "H. Peter Anvin" <hpa@...or.com> CC: <x86@...nel.org> CC: Brian Norris <computersforpeace@...il.com> Signed-off-by: Mark Rustad <mark.d.rustad@...el.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com> --- arch/x86/ia32/syscall_ia32.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/ia32/syscall_ia32.c b/arch/x86/ia32/syscall_ia32.c index 4754ba0..7bc553b 100644 --- a/arch/x86/ia32/syscall_ia32.c +++ b/arch/x86/ia32/syscall_ia32.c @@ -15,6 +15,7 @@ typedef void (*sys_call_ptr_t)(void); extern void compat_ni_syscall(void); +DIAG_PUSH DIAG_CLANG_IGNORE(initializer-overrides) const sys_call_ptr_t ia32_sys_call_table[__NR_ia32_syscall_max+1] = { /* * Smells like a compiler bug -- it doesn't work @@ -23,3 +24,4 @@ const sys_call_ptr_t ia32_sys_call_table[__NR_ia32_syscall_max+1] = { [0 ... __NR_ia32_syscall_max] = &compat_ni_syscall, #include <asm/syscalls_32.h> }; +DIAG_POP -- 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists