Messages in this thread | | | From | Arnd Bergmann <> | Date | Fri, 21 Jun 2019 11:43:58 +0200 | Subject | Re: [PATCH] structleak: disable BYREF_ALL in combination with KASAN_STACK |
| |
On Thu, Jun 20, 2019 at 7:36 PM Kees Cook <keescook@chromium.org> wrote: > > On Tue, Jun 18, 2019 at 11:47:13AM +0200, Arnd Bergmann wrote: > > The combination of KASAN_STACK and GCC_PLUGIN_STRUCTLEAK_BYREF_ALL > > leads to much larger kernel stack usage, as seen from the warnings > > about functions that now exceed the 2048 byte limit: > > Is the preference that this go into v5.2 (there's not much time left), > or should this be v5.3? (You didn't mark it as Cc: stable?)
Having it in 5.2 would be great. I had not done much build testing in the last months, so I didn't actually realize that your patch was merged a while ago rather than only in linux-next.
BTW, I have now run into a small number of files that are still affected by a stack overflow warning from STRUCTLEAK_BYREF_ALL. I'm trying to come up with patches for those as well, we can probably do it in a way that also improves the affected drivers. I'll put you on Cc when I find another one.
Arnd
| |