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: Wed, 6 Oct 2021 16:22:38 +0200 From: Vincenzo Frascino <vincenzo.frascino@....com> To: Marco Elver <elver@...gle.com> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, kasan-dev@...glegroups.com, Andrew Morton <akpm@...ux-foundation.org>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Dmitry Vyukov <dvyukov@...gle.com>, Andrey Ryabinin <aryabinin@...tuozzo.com>, Alexander Potapenko <glider@...gle.com>, Evgenii Stepanov <eugenis@...gle.com>, Branislav Rankov <Branislav.Rankov@....com>, Andrey Konovalov <andreyknvl@...il.com>, Lorenzo Pieralisi <lorenzo.pieralisi@....com> Subject: Re: [PATCH v2 5/5] kasan: Extend KASAN mode kernel parameter On 10/6/21 1:35 PM, Marco Elver wrote: >> +static inline bool kasan_sync_fault_possible(void) >> +{ >> + return !kasan_flag_async | kasan_flag_asymm; >> } > Is the choice of bit-wise OR a typo? Because this should probably have > been logical OR. In this case, functionally it shouldn't matter, but is > unusual style. Good catch! This is clearly a typo and a copy-paste of a typo ;) -- Regards, Vincenzo
Powered by blists - more mailing lists