[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6cc0eadc-5204-ce36-f5e8-88ba76bb6826@virtuozzo.com>
Date: Tue, 13 Dec 2016 12:20:40 +0300
From: Andrey Ryabinin <aryabinin@...tuozzo.com>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Maninder Singh <maninder1.s@...sung.com>
CC: Alexander Potapenko <glider@...gle.com>,
Jonathan Corbet <corbet@....net>,
Michal Marek <mmarek@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
kasan-dev <kasan-dev@...glegroups.com>,
<linux-doc@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
"open list:KERNEL BUILD + fi..." <linux-kbuild@...r.kernel.org>,
PANKAJ MISHRA <pankaj.m@...sung.com>,
"Ajeet Kumar Yadav" <ajeet.y@...sung.com>,
Vaneet narang <v.narang@...sung.com>
Subject: Re: [PATCH v2] kasan: Support for r/w instrumentation control
On 12/13/2016 11:58 AM, Dmitry Vyukov wrote:
> --- a/Documentation/dev-tools/kasan.rst
> +++ b/Documentation/dev-tools/kasan.rst
> @@ -40,6 +40,14 @@ similar to the following to the respective kernel Makefile:
>
> KASAN_SANITIZE := n
>
> +Sometimes it may be useful to disable instrumentation of reads, or writes
> +or both for the entire kernel. For example, if binary size is a concern,
> +it may be useful to disable instrumentation of reads to reduce binary size but
> +still catch more harmful bugs on writes. Or, if one is interested only in
> +sanitization of a particular module and performance is a concern, she can
> +disable instrumentation of both reads and writes for kernel code.
> +Instrumentation can be disabled with CONFIG_KASAN_READS and
> CONFIG_KASAN_WRITES.
> +
I don't understand this. How this can be related to modules? Configs are global.
You can't just disable/enable config per module.
> Error reports
>
Powered by blists - more mailing lists