From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: axelrasmussen@google.com, mhiramat@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] tracing: Change STR_VAR_MAX_LEN
Date: Fri, 02 Oct 2020 17:04:46 -0500 [thread overview]
Message-ID: <75577192da2769b982b748305ad5609d94bd9bcf.camel@kernel.org> (raw)
In-Reply-To: <20201002154417.320ad78b@gandalf.local.home>
Hi Steve,
On Fri, 2020-10-02 at 15:44 -0400, Steven Rostedt wrote:
> On Thu, 1 Oct 2020 16:46:44 -0500
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > 32 is too small for this value, and anyway it makes more sense to
> > use
> > MAX_FILTER_STR_VAL, as this is also the value used for variable-
> > length
> > __strings.
> >
> > Tested-by: Axel Rasmussen <axelrasmussen@google.com>
> > Signed-off-by: Tom Zanussi <zanussi@kernel.org>
> > ---
> > kernel/trace/trace_synth.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace_synth.h
> > b/kernel/trace/trace_synth.h
> > index ac35c45207c4..5166705d1556 100644
> > --- a/kernel/trace/trace_synth.h
> > +++ b/kernel/trace/trace_synth.h
> > @@ -7,7 +7,7 @@
> > #define SYNTH_SYSTEM "synthetic"
> > #define SYNTH_FIELDS_MAX 32
> >
> > -#define STR_VAR_LEN_MAX 32 /* must be multiple of
> > sizeof(u64) */
> > +#define STR_VAR_LEN_MAX MAX_FILTER_STR_VAL /* must be
> > multiple of sizeof(u64) */
>
> Hmm, this requirement is now passed to MAX_FILTER_STR_VAL, but
> there's no
> mention of it there. I guess we should have a
>
> BUILD_BUG_ON(STR_VAR_LEN_MAX & (sizeof(u64) - 1));
>
> in C code somewhere.
Good point. I'll add that in the next version.
Thanks,
Tom
next prev parent reply other threads:[~2020-10-02 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 21:46 [PATCH v3 0/3] tracing: Add dynamic strings for synthetic events Tom Zanussi
2020-10-01 21:46 ` [PATCH v3 1/3] tracing: Change STR_VAR_MAX_LEN Tom Zanussi
2020-10-02 19:44 ` Steven Rostedt
2020-10-02 22:04 ` Tom Zanussi [this message]
2020-10-01 21:46 ` [PATCH v3 2/3] tracing: Fix parse_synth_field() error handling Tom Zanussi
2020-10-01 21:46 ` [PATCH v3 3/3] tracing: Add support for dynamic strings to synthetic events Tom Zanussi
2020-10-03 0:55 ` [PATCH v3 0/3] tracing: Add dynamic strings for " Steven Rostedt
2020-10-03 1:00 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75577192da2769b982b748305ad5609d94bd9bcf.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome