linux-next: manual merge of the akpm-current tree with the kspp tree
From: Stephen Rothwell
Date: Wed Feb 13 2019 - 01:04:25 EST
Today's linux-next merge of the akpm-current tree got a conflict in:
9219e54be983 ("gcc-plugins: structleak: Generalize to all variable types")
from the kspp tree and commit:
7fabedf42152 ("kasan: remove use after scope bugs detection.")
from the akpm-current tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
diff --cc scripts/gcc-plugins/Kconfig
@@@ -67,22 -67,13 +67,18 @@@ config GCC_PLUGIN_LATENT_ENTROP
- bool "Force initialization of variables containing userspace addresses"
+ bool "Zero initialize stack variables"
- # Currently STRUCTLEAK inserts initialization out of live scope of
- # variables from KASAN point of view. This leads to KASAN false
- # positive reports. Prohibit this combination for now.
- depends on !KASAN_EXTRA
- This plugin zero-initializes any structures containing a
- __user attribute. This can prevent some classes of information
- This plugin was ported from grsecurity/PaX. More information at:
+ While the kernel is built with warnings enabled for any missed
+ stack variable initializations, this warning is silenced for
+ anything passed by reference to another function, under the
+ occasionally misguided assumption that the function will do
+ the initialization. As this regularly leads to exploitable
+ flaws, this plugin is available to identify and zero-initialize
+ such variables, depending on the chosen level of coverage.
+ This plugin was originally ported from grsecurity/PaX. More
+ information at:
Description: OpenPGP digital signature