[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161115154002.0c4c7a5e1fd23f12474fc80e@linux-foundation.org>
Date: Tue, 15 Nov 2016 15:40:02 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: aryabinin@...tuozzo.com, glider@...gle.com,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kasan: support use-after-scope detection
On Tue, 15 Nov 2016 17:07:25 +0100 Dmitry Vyukov <dvyukov@...gle.com> wrote:
> Gcc revision 241896 implements use-after-scope detection.
> Will be available in gcc 7. Support it in KASAN.
>
> Gcc emits 2 new callbacks to poison/unpoison large stack
> objects when they go in/out of scope.
> Implement the callbacks and add a test.
>
> ...
>
> --- a/lib/test_kasan.c
> +++ b/lib/test_kasan.c
> @@ -411,6 +411,29 @@ static noinline void __init copy_user_test(void)
> kfree(kmem);
> }
>
> +static noinline void __init use_after_scope_test(void)
This reader has no idea why this code uses noinline, and I expect
others will have the same issue.
Can we please get a code comment in there to reveal the reason?
Powered by blists - more mailing lists