On Sat, Mar 2, 2019 at 2:16 PM Arnd Bergmann <[email protected]> wrote: > > On Sat, Mar 2, 2019 at 4:43 PM Kees Cook <[email protected]> wrote: > > > > On Sat, Mar 2, 2019 at 1:05 AM Ard Biesheuvel <[email protected]> > > wrote: > > > > > > On Thu, 28 Feb 2019 at 21:27, Arnd Bergmann <[email protected]> wrote: > > > > I get similar results with asan-stack=1 but without your plugin, only > > > > the combination of the two has the explosive stack size growth. > > > > I can look more closely, but I'm not sure it's entirely worth it: > > these two may not make sense to build at the same time. (e.g. the > > use-after-scope config was disallowed to work with this plugin.) > > Well, I still want to make sure all 'randconfig' builds complete without > warnings, and without having to turn off the otherwise useful > stack overflow warnings. > > One thing I noticed is that your patch removes the 'depends on > !COMPILE_TEST' check for GCC_PLUGIN_STRUCTLEAK_BYREF_ALL, > so if we add that back in, it would at least take care of the > allmodconfig and randconfig cases.
Okay, I'll add this back in the next few days. -- Kees Cook
