From: Andrey Ryabinin
> Sent: 03 March 2017 13:50
...
> noinline_iff_kasan might be a better name. noinline_for_kasan gives the
> impression
> that we always noinline function for the sake of kasan, while
> noinline_iff_kasan
> clearly indicates that function is noinline only if kasan is used.
From: Andrey Ryabinin
> Sent: 03 March 2017 13:50
...
> noinline_iff_kasan might be a better name. noinline_for_kasan gives the
> impression
> that we always noinline function for the sake of kasan, while
> noinline_iff_kasan
> clearly indicates that function is noinline only if kasan is used.
On Fri, Mar 3, 2017 at 3:33 PM, Alexander Potapenko wrote:
> On Fri, Mar 3, 2017 at 3:30 PM, Arnd Bergmann wrote:
>> On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko
>> wrote:
>>
>> Would KMSAN also force local variables to be
On Fri, Mar 3, 2017 at 3:33 PM, Alexander Potapenko wrote:
> On Fri, Mar 3, 2017 at 3:30 PM, Arnd Bergmann wrote:
>> On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko
>> wrote:
>>
>> Would KMSAN also force local variables to be non-overlapping the way that
>> asan-stack=1 and
On Fri, Mar 3, 2017 at 3:30 PM, Arnd Bergmann wrote:
> On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko wrote:
>> On Fri, Mar 3, 2017 at 2:50 PM, Andrey Ryabinin
>> wrote:
>
@@ -416,6 +416,17 @@ static __always_inline void
On Fri, Mar 3, 2017 at 3:30 PM, Arnd Bergmann wrote:
> On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko wrote:
>> On Fri, Mar 3, 2017 at 2:50 PM, Andrey Ryabinin
>> wrote:
>
@@ -416,6 +416,17 @@ static __always_inline void
__write_once_size(volatile void *p, void *res, int s
On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko wrote:
> On Fri, Mar 3, 2017 at 2:50 PM, Andrey Ryabinin
> wrote:
>>> @@ -416,6 +416,17 @@ static __always_inline void __write_once_size(volatile
>>> void *p, void *res, int s
>>> */
>>> #define
On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko wrote:
> On Fri, Mar 3, 2017 at 2:50 PM, Andrey Ryabinin
> wrote:
>>> @@ -416,6 +416,17 @@ static __always_inline void __write_once_size(volatile
>>> void *p, void *res, int s
>>> */
>>> #define noinline_for_stack noinline
>>>
>>> +/*
>>>
On Fri, Mar 3, 2017 at 2:50 PM, Andrey Ryabinin wrote:
>
>
> On 03/02/2017 07:38 PM, Arnd Bergmann wrote:
>> When CONFIG_KASAN is set, we can run into some code that uses incredible
>> amounts of kernel stack:
>>
>> drivers/staging/dgnc/dgnc_neo.c:1056:1: error: the frame
On Fri, Mar 3, 2017 at 2:50 PM, Andrey Ryabinin wrote:
>
>
> On 03/02/2017 07:38 PM, Arnd Bergmann wrote:
>> When CONFIG_KASAN is set, we can run into some code that uses incredible
>> amounts of kernel stack:
>>
>> drivers/staging/dgnc/dgnc_neo.c:1056:1: error: the frame size of 2 bytes
>>
On 03/02/2017 07:38 PM, Arnd Bergmann wrote:
> When CONFIG_KASAN is set, we can run into some code that uses incredible
> amounts of kernel stack:
>
> drivers/staging/dgnc/dgnc_neo.c:1056:1: error: the frame size of 2 bytes
> is larger than 2048 bytes [-Werror=frame-larger-than=]
>
On 03/02/2017 07:38 PM, Arnd Bergmann wrote:
> When CONFIG_KASAN is set, we can run into some code that uses incredible
> amounts of kernel stack:
>
> drivers/staging/dgnc/dgnc_neo.c:1056:1: error: the frame size of 2 bytes
> is larger than 2048 bytes [-Werror=frame-larger-than=]
>
When CONFIG_KASAN is set, we can run into some code that uses incredible
amounts of kernel stack:
drivers/staging/dgnc/dgnc_neo.c:1056:1: error: the frame size of 2 bytes is
larger than 2048 bytes [-Werror=frame-larger-than=]
drivers/media/i2c/cx25840/cx25840-core.c:4960:1: error: the frame
When CONFIG_KASAN is set, we can run into some code that uses incredible
amounts of kernel stack:
drivers/staging/dgnc/dgnc_neo.c:1056:1: error: the frame size of 2 bytes is
larger than 2048 bytes [-Werror=frame-larger-than=]
drivers/media/i2c/cx25840/cx25840-core.c:4960:1: error: the frame
14 matches
Mail list logo