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, 21 Jan 2021 11:34:01 +0000 From: Vincenzo Frascino <vincenzo.frascino@....com> To: Andrey Konovalov <andreyknvl@...gle.com> Cc: Catalin Marinas <catalin.marinas@....com>, LKML <linux-kernel@...r.kernel.org>, kasan-dev <kasan-dev@...glegroups.com>, Leon Romanovsky <leonro@...lanox.com>, Alexander Potapenko <glider@...gle.com>, Linux ARM <linux-arm-kernel@...ts.infradead.org>, Andrey Ryabinin <aryabinin@...tuozzo.com>, Dmitry Vyukov <dvyukov@...gle.com> Subject: Re: [PATCH] kasan: Add explicit preconditions to kasan_report() Hi Andrey, On 1/19/21 8:56 PM, Andrey Konovalov wrote: >> return (is_vmalloc_addr(addr) || virt_addr_valid(addr)); > Do we need is_vmalloc_addr()? As we don't yet have vmalloc support for HW_TAGS. It is not necessary but it does not hurt, since we are going to add vmalloc anyway at some point, I would keep it here. -- Regards, Vincenzo
Powered by blists - more mailing lists