linux-kernel - Re: [PATCH tracing 0/3] tracing: support

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20230425132028.7d16e04c@gandalf.local.home>
Date:   Tue, 25 Apr 2023 13:20:28 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Alan Maguire <alan.maguire@...cle.com>
Cc:     "Masami Hiramatsu (Google)" <mhiramat@...nel.org>, corbet@....net,
        shuah@...nel.org, linux-kernel@...r.kernel.org,
        linux-trace-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kselftest@...r.kernel.org
Subject: Re: [PATCH tracing 0/3] tracing: support > 8 byte filter predicates

On Tue, 25 Apr 2023 18:15:03 +0100
Alan Maguire <alan.maguire@...cle.com> wrote:

> that's a great idea; what would be the most consistent ftrace syntax
> for this do you think? I noticed that hist triggers append a modifier
> to the field name so would something like
> 
> "dst.ipv6 == ::1"

Yeah, I think just having ":" in the name without quotes can help the filter
know that it's a ipv6 id.

Hmm, although we may want to do the same for mac addresses. But we can
determine the difference by the field size. If it's 6 bytes, it's a mac, if
it's 128 bits, then ipv6.

-- Steve