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: Thu, 16 Jan 2020 09:50:53 +0100 From: Dmitry Vyukov <dvyukov@...gle.com> To: Patricia Alfonso <trishalfonso@...gle.com> Cc: Jeff Dike <jdike@...toit.com>, Richard Weinberger <richard@....at>, anton.ivanov@...bridgegreys.com, Andrey Ryabinin <aryabinin@...tuozzo.com>, David Gow <davidgow@...gle.com>, Brendan Higgins <brendanhiggins@...gle.com>, linux-um@...ts.infradead.org, kasan-dev <kasan-dev@...glegroups.com>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [RFC PATCH] UML: add support for KASAN under x86_64 On Wed, Jan 15, 2020 at 7:28 PM Patricia Alfonso <trishalfonso@...gle.com> wrote: > > Make KASAN run on User Mode Linux on x86_64. > diff --git a/arch/um/kernel/Makefile b/arch/um/kernel/Makefile > index 5aa882011e04..f783a7dd863c 100644 > --- a/arch/um/kernel/Makefile > +++ b/arch/um/kernel/Makefile > @@ -8,6 +8,9 @@ > # kernel. > KCOV_INSTRUMENT := n > > +# Do not instrument on main.o It's always good to explain why. Otherwise it will be stuck there forever because nobody really knows why and if they will break something by removing it. This comment is also somewhat confusing. We don't instrument the whole dir, not just main.c? Should we ignore just this single file as comment says? > +KASAN_SANITIZE := n > +
Powered by blists - more mailing lists