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, 6 Jul 2017 17:09:31 -0700 From: Greg Hackmann <ghackmann@...gle.com> To: Andrey Ryabinin <aryabinin@...tuozzo.com>, Alexander Potapenko <glider@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>, Masahiro Yamada <yamada.masahiro@...ionext.com>, Michal Marek <mmarek@...e.com> Cc: linux-kernel@...r.kernel.org, kasan-dev@...glegroups.com, linux-mm@...ck.org, linux-kbuild@...r.kernel.org, Matthias Kaehlcke <mka@...omium.org>, Michael Davidson <md@...gle.com> Subject: Re: [PATCH 1/4] kasan: support alloca() poisoning On 07/06/2017 03:01 PM, Greg Hackmann wrote: > @@ -101,6 +101,9 @@ static const char *get_shadow_bug_type(struct kasan_access_info *info) > break; > case KASAN_USE_AFTER_SCOPE: > bug_type = "use-after-scope"; > + case KASAN_ALLOCA_LEFT: > + case KASAN_ALLOCA_RIGHT: > + bug_type = "alloca-out-of-bounds"; > break; > } There needs to be a "break" above the new case statements. I'll wait to see if there's any other feedback, then send out a V2 patch that fixes this.
Powered by blists - more mailing lists