linux-kernel - Re: [GIT PULL] tracing: Two event pid filtering bug fixes

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: <CAHk-=wiJn3L26=1m4RAeGJ-PFQkrqGNCgdH1bWu7+XJKtwfvgw@mail.gmail.com>
Date:   Sat, 27 Nov 2021 12:12:55 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Ingo Molnar <mingo@...nel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Tom Zanussi <zanussi@...nel.org>,
        Tzvetomir Stoyanov <tz.stoyanov@...il.com>
Subject: Re: [GIT PULL] tracing: Two event pid filtering bug fixes

On Sat, Nov 27, 2021 at 10:28 AM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Two fixes to event pid filtering:
>
> - Have created events reflect the current state of pid filtering
>
> - Test pid filtering on discard test of recorded logic.
>   (Also clean up the if statement to be cleaner).

I could not parse either of those statements. The second one in
particular is just a jumble of random words in a random order.

I tried to make it make sense by looking at the commits themselves,
but who knows. Maybe I made it worse by turning it from
incomprehensible to actively wrong.

Please make those explanations more clear in the future, ok?

               Linus