summaryrefslogtreecommitdiffstats
path: root/arch/x86/entry/vsyscall
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2016-11-10 17:44:51 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2016-11-11 17:45:08 +0100
commitbeae2c9eb500d5509feb9fd148d34d97a9b1d276 (patch)
tree244e9a22766e79ecbbabe1debc633bcf7551c586 /arch/x86/entry/vsyscall
parentrc: print correct variable for z8f0811 (diff)
downloadlinux-beae2c9eb500d5509feb9fd148d34d97a9b1d276.tar.xz
linux-beae2c9eb500d5509feb9fd148d34d97a9b1d276.zip
crypto: aesni: shut up -Wmaybe-uninitialized warning
The rfc4106 encrypy/decrypt helper functions cause an annoying false-positive warning in allmodconfig if we turn on -Wmaybe-uninitialized warnings again: arch/x86/crypto/aesni-intel_glue.c: In function ‘helper_rfc4106_decrypt’: include/linux/scatterlist.h:67:31: warning: ‘dst_sg_walk.sg’ may be used uninitialized in this function [-Wmaybe-uninitialized] The problem seems to be that the compiler doesn't track the state of the 'one_entry_in_sg' variable across the kernel_fpu_begin/kernel_fpu_end section. This takes the easy way out by adding a bogus initialization, which should be harmless enough to get the patch into v4.9 so we can turn on this warning again by default without producing useless output. A follow-up patch for v4.10 rearranges the code to make the warning go away. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/x86/entry/vsyscall')
0 files changed, 0 insertions, 0 deletions