lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 13 Dec 2016 10:38:14 +0100 From: Dmitry Vyukov <dvyukov@...gle.com> To: Andrey Ryabinin <aryabinin@...tuozzo.com> Cc: Maninder Singh <maninder1.s@...sung.com>, 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 Tue, Dec 13, 2016 at 10:20 AM, Andrey Ryabinin <aryabinin@...tuozzo.com> wrote: > > > 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. Build everything without instrumentation. Then enable instrumentation and do "make lib/test_kasan.ko". Or build everything, copy out bzImage, change config, build everything again.
Powered by blists - more mailing lists