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: Tue, 19 May 2020 17:09:58 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Andrey Konovalov <andreyknvl@...gle.com> Cc: Marco Elver <elver@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>, Alexander Potapenko <glider@...gle.com>, LKML <linux-kernel@...r.kernel.org>, kasan-dev <kasan-dev@...glegroups.com>, Andrey Ryabinin <aryabinin@...tuozzo.com>, Linux Memory Management List <linux-mm@...ck.org>, kernel test robot <rong.a.chen@...el.com> Subject: Re: [PATCH] kasan: Disable branch tracing for core runtime On Tue, 19 May 2020 23:05:46 +0200 Andrey Konovalov <andreyknvl@...gle.com> wrote: > On Tue, May 19, 2020 at 8:25 PM Marco Elver <elver@...gle.com> wrote: > > > > During early boot, while KASAN is not yet initialized, it is possible to > > enter reporting code-path and end up in kasan_report(). While > > uninitialized, the branch there prevents generating any reports, > > however, under certain circumstances when branches are being traced > > (TRACE_BRANCH_PROFILING), we may recurse deep enough to cause kernel > > reboots without warning. > > > > To prevent similar issues in future, we should disable branch tracing > > for the core runtime. > > > > ... > > Reviewed-by: Andrey Konovalov <andreyknvl@...gle.com> Thanks, I queued this for 5.7.
Powered by blists - more mailing lists