linux-kernel - Re: [PATCH] tracing: Add common

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: <20250409113404.5b2085a7@gandalf.local.home>
Date: Wed, 9 Apr 2025 11:34:04 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
 <linux-trace-kernel@...r.kernel.org>, Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>, Tom Zanussi <zanussi@...nel.org>
Subject: Re: [PATCH] tracing: Add common_comm to histograms

On Wed, 9 Apr 2025 08:32:44 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:

> BTW, the string field size must always be MAX_FILTER_STR_VAL (for comparing
> with other string filters, which checks the size at first.)
> Somewhere we should comment it.

I believe that's more of an implementation detail of the underlining
infrastructure. I don't think it matters for the users of the interface. It
may be a limitation in max size.

Is that what you want to comment? That the string held (for all strings)
has a max size defined by the MAX_FILTER_STR_VAL, which currently is 256?

-- Steve