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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 24 Jan 2022 18:59:40 +0100 From: Marco Elver <elver@...gle.com> To: Andrey Konovalov <andreyknvl@...il.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Andrey Ryabinin <ryabinin.a.a@...il.com>, Alexander Potapenko <glider@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>, kasan-dev <kasan-dev@...glegroups.com>, LKML <linux-kernel@...r.kernel.org>, Linux Memory Management List <linux-mm@...ck.org>, Kees Cook <keescook@...omium.org>, Brendan Higgins <brendanhiggins@...gle.com>, linux-hardening@...r.kernel.org, Nico Pache <npache@...hat.com> Subject: Re: [PATCH] kasan: test: fix compatibility with FORTIFY_SOURCE On Mon, 24 Jan 2022 at 18:54, Andrey Konovalov <andreyknvl@...il.com> wrote: > > -On Mon, Jan 24, 2022 at 5:07 PM Marco Elver <elver@...gle.com> wrote: > > > > With CONFIG_FORTIFY_SOURCE enabled, string functions will also perform > > dynamic checks using __builtin_object_size(ptr), which when failed will > > panic the kernel. > > > > Because the KASAN test deliberately performs out-of-bounds operations, > > the kernel panics with FORITY_SOURCE, for example: > > Nit: FORITY_SOURCE -> FORTIFY_SOURCE How did that happen?! My hands need some better synchronization... I'll refrain sending a v2, assuming Andrew can fix up this spelling mistake upon applying. [...] > > Reviewed-by: Andrey Konovalov <andreyknvl@...il.com> Thanks!
Powered by blists - more mailing lists