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 v2 4/7] tracing: Add synthetic event error logging
Date: Mon, 12 Oct 2020 17:24:13 -0500 [thread overview]
Message-ID: <3e516b408adeaf6969e267a52c94b66c7579c83d.camel@kernel.org> (raw)
In-Reply-To: <20201012180439.22ed7e4f@oasis.local.home>
Hi Steve,
On Mon, 2020-10-12 at 18:04 -0400, Steven Rostedt wrote:
> On Mon, 12 Oct 2020 15:18:06 -0500
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > +static int cmdstr_append(char *buf, const char *str, int
> > *remaining)
> > +{
> > + int len = strlen(str);
> > +
> > + if (len + 1 >= *remaining) {
> > + synth_err(SYNTH_ERR_CMD_TOO_LONG, 0);
> > + return -EINVAL;
> > + }
> > +
> > + strcat(buf, str);
> > + strcat(buf, " ");
> > + *remaining -= len + 1;
> > +
> > + return 0;
> > +}
> > +
> > +static int save_cmdstr(int argc, const char *name, const char
> > **argv)
> > +{
> > + int i, ret, remaining = MAX_DYNEVENT_CMD_LEN;
> > + char *buf;
> > +
> > + synth_err_clear();
> > +
> > + buf = kzalloc(MAX_DYNEVENT_CMD_LEN, GFP_KERNEL);
> > + if (!buf)
> > + return -ENOMEM;
> > +
> > + ret = cmdstr_append(buf, name, &remaining);
> > + if (ret) {
> > + kfree(buf);
> > + return ret;
> > + }
> > +
> > + for (i = 0; i < argc; i++) {
> > + ret = cmdstr_append(buf, argv[i], &remaining);
> > + if (ret) {
> > + kfree(buf);
> > + return ret;
> > + }
> > + }
> > +
> > + last_cmd_set(buf);
> > +
> > + kfree(buf);
> > +
> > + return ret;
> > +}
> > +
>
> Hmm, the above could easily be replaced with:
>
> struct seq_buf s;
>
> buf = kzalloc(MAX_DYNEVENT_CMD_LEN, GFP_KERNEL);
> if (!buf)
> return -ENOMEM;
>
> seq_buf_init(&s, buf, MAX_DYNEVENT_CMD_LEN);
>
> seq_buf_puts(&s, name);
>
> for (i = 0; i < argc; i++) {
> seq_buf_putc(&s, ' ');
> seq_buf_puts(&s, argv[i]);
> }
>
> if (!seq_buf_buffer_left(&s)) {
> synth_err(SYNTH_ERR_CMD_TOO_LONG, 0);
> kfree(buf);
> return -EINVAL;
> }
> buf[s.len] = 0;
> last_cmd_set(buf);
>
> kfree(buf);
> return 0;
>
Yeah, that makes sense, will change it.
Thanks,
Tom
>
> -- Steve
next prev parent reply other threads:[~2020-10-12 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:18 [PATCH v2 0/7] tracing: Synthetic event dynamic string fixes Tom Zanussi
2020-10-12 20:18 ` [PATCH v2 1/7] tracing: Don't show dynamic string internals in synthetic event description Tom Zanussi
2020-10-12 20:18 ` [PATCH v2 2/7] tracing: Move is_good_name() from trace_probe.h to trace.h Tom Zanussi
2020-10-12 20:18 ` [PATCH v2 3/7] tracing: Check that the synthetic event and field names are legal Tom Zanussi
2020-10-12 20:18 ` [PATCH v2 4/7] tracing: Add synthetic event error logging Tom Zanussi
2020-10-12 21:42 ` Steven Rostedt
2020-10-12 21:49 ` Steven Rostedt
2020-10-12 21:59 ` Tom Zanussi
2020-10-12 22:04 ` Steven Rostedt
2020-10-12 22:24 ` Tom Zanussi [this message]
2020-10-12 20:18 ` [PATCH v2 5/7] selftests/ftrace: Change synthetic event name for inter-event-combined test Tom Zanussi
2020-10-12 20:18 ` [PATCH v2 6/7] tracing: Handle synthetic event array field type checking correctly Tom Zanussi
2020-10-12 22:14 ` Steven Rostedt
2020-10-12 22:24 ` Tom Zanussi
2020-10-12 20:18 ` [PATCH v2 7/7] selftests/ftrace: Add test case for synthetic event syntax errors Tom Zanussi
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=3e516b408adeaf6969e267a52c94b66c7579c83d.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
all inboxes | Powered by JetHome®