linux-kernel - Re: [PATCH V9 01/16] rv: Add Runtime Verification (RV) interface

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YuWrI18qjmnOOPEE@geo.homenetwork>
Date:   Sun, 31 Jul 2022 06:05:23 +0800
From:   Tao Zhou <tao.zhou@...ux.dev>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Daniel Bristot de Oliveira <bristot@...nel.org>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Jonathan Corbet <corbet@....net>,
        Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>,
        Will Deacon <will@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Marco Elver <elver@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Gabriele Paoloni <gpaoloni@...hat.com>,
        Juri Lelli <juri.lelli@...hat.com>,
        Clark Williams <williams@...hat.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-trace-devel@...r.kernel.org, Tao Zhou <tao.zhou@...ux.dev>
Subject: Re: [PATCH V9 01/16] rv: Add Runtime Verification (RV) interface

On Sat, Jul 30, 2022 at 01:01:45PM -0400, Steven Rostedt wrote:
> #define rv_attach_trace_probe(monitor, tp, rv_handler)                                  \
>         ({                                                                            \
>                 check_trace_callback_type_##tp(rv_handler);                             \
>                 WARN_ONCE(register_trace_##tp(rv_handler, NULL),                        \
>                                 "fail attaching " #monitor " " #tp "handler");          \
>         })
> 
> Where the macro returns the result of the WARN_ONCE() which is zero on
> success (no warning) and non-zero otherwise.

The modification of macro make sense to me even though I do not know trace enough. Thanks,