Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-13 Thread Arnd Bergmann
On Fri, Feb 10, 2017 at 2:24 PM, Arnd Bergmann wrote: > On Thu, Feb 9, 2017 at 6:00 PM, Arnd Bergmann wrote: >> To reduce this risk, -fsanitize-address-use-after-scope is now split out >> into a separate Kconfig option, which cannot be selected at the same time >> as CONFIG_KASAN_INLINE, leading

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-10 Thread Arnd Bergmann
On Thu, Feb 9, 2017 at 6:00 PM, Arnd Bergmann wrote: > To reduce this risk, -fsanitize-address-use-after-scope is now split out > into a separate Kconfig option, which cannot be selected at the same time > as CONFIG_KASAN_INLINE, leading to stack frames that are smaller than 2 > kilobytes most of

RE: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-10 Thread David Laight
From: David Miller > Sent: 09 February 2017 21:31 > From: Arnd Bergmann > Date: Wed, 8 Feb 2017 22:18:26 +0100 > > > When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large > > stack frames in some functions. This goes unnoticed normally because > > CONFIG_FRAME_WARN is disa

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread David Miller
From: Arnd Bergmann Date: Wed, 8 Feb 2017 22:18:26 +0100 > When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large > stack frames in some functions. This goes unnoticed normally because > CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit > 3f181b4d8652

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread Arnd Bergmann
On Thursday, February 9, 2017 4:51:25 PM CET Dmitry Vyukov wrote: > On Thu, Feb 9, 2017 at 3:33 PM, Arnd Bergmann wrote: > >>> > >>> Thanks for the list, that looks very helpful. The ones I found myself > >>> seem to be a strict (and small) subset of those, using gcc-7.0.1 on x86-64 > >>> with all

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread Dmitry Vyukov
On Thu, Feb 9, 2017 at 3:33 PM, Arnd Bergmann wrote: >>> >>> Thanks for the list, that looks very helpful. The ones I found myself >>> seem to be a strict (and small) subset of those, using gcc-7.0.1 on x86-64 >>> with allmodconfig and a few hundred randconfig builds. Which compiler >>> version di

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread Arnd Bergmann
On Thu, Feb 9, 2017 at 1:46 PM, Dmitry Vyukov wrote: > On Thu, Feb 9, 2017 at 12:55 PM, Arnd Bergmann wrote: >> On Thu, Feb 9, 2017 at 12:28 PM, Dmitry Vyukov wrote: >>> On Wed, Feb 8, 2017 at 10:18 PM, Arnd Bergmann wrote: >> >> Thanks for the list, that looks very helpful. The ones I found my

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread Dmitry Vyukov
On Thu, Feb 9, 2017 at 12:55 PM, Arnd Bergmann wrote: > On Thu, Feb 9, 2017 at 12:28 PM, Dmitry Vyukov wrote: >> On Wed, Feb 8, 2017 at 10:18 PM, Arnd Bergmann wrote: >>> When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large >>> stack frames in some functions. This goes un

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread Arnd Bergmann
On Thu, Feb 9, 2017 at 12:28 PM, Dmitry Vyukov wrote: > On Wed, Feb 8, 2017 at 10:18 PM, Arnd Bergmann wrote: >> When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large >> stack frames in some functions. This goes unnoticed normally because >> CONFIG_FRAME_WARN is disabled wi

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-09 Thread Dmitry Vyukov
On Wed, Feb 8, 2017 at 10:18 PM, Arnd Bergmann wrote: > When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large > stack frames in some functions. This goes unnoticed normally because > CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit > 3f181b4d8652 ("lib

[PATCH] netlink: move nla_put_{u8,u16,u32} out of line

2017-02-08 Thread Arnd Bergmann
When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large stack frames in some functions. This goes unnoticed normally because CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit 3f181b4d8652 ("lib/Kconfig.debug: disable -Wframe-larger-than warnings with KASAN