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: Fri, 15 Jan 2021 11:17:53 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Alexander Potapenko <glider@...gle.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, Marco Elver <elver@...gle.com>, Andrey Konovalov <andreyknvl@...il.com>, Dmitry Vyukov <dvyukov@...gle.com>, Ingo Molnar <mingo@...hat.com>, Petr Mladek <pmladek@...e.com>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Linux Memory Management List <linux-mm@...ck.org> Subject: Re: [PATCH 1/4] tracing: add error_report trace points On Fri, 15 Jan 2021 13:53:19 +0100 Alexander Potapenko <glider@...gle.com> wrote: > > #define REPORT_TOOL_LIST \ > > EM(KFENCE, kfence) \ > > EMe(KASAN, kasan) > > Thanks, will be done in v2! > Note that checkpatch doesn't really like this declaration style, > claiming that "Macros with complex values should be enclosed in > parentheses". > (although it is consistent with what's done in other trace event headers) checkpatch.pl hates most of the tracing macro code ;-) It's the one place that you can mostly ignore checkpatch reports. -- Steve
Powered by blists - more mailing lists