From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joelaf@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Michael Sartain <mikesart@gmail.com>,
kernel-team@android.com, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v4 1/3] tracing: Add support for recording tgid of tasks
Date: Mon, 26 Jun 2017 15:28:07 -0400 [thread overview]
Message-ID: <20170626152807.7d40edb7@gandalf.local.home> (raw)
In-Reply-To: <CAJWu+oqbEuT3cKGVJ_bQAxR5ra_2_CWtSNzb8XpRTPfFQG3K-Q@mail.gmail.com>
On Mon, 26 Jun 2017 12:10:04 -0700
Joel Fernandes <joelaf@google.com> wrote:
> > That seems Ok with me to do, I think a valid point.
> >
> > I think that I should do it in the second call to
> > tracing_start_tgid_record too then (__ftrace_event_enable_disable) to
> > error out if the allocation fails.
> >
> > While going this code I again, I noticed another potential issue in
> > __ftrace_event_enable_disable
>
> Sorry I hit send too soon!
>
> I was saying, While going through this code again I noticed another
> potential issue in __ftrace_event_enable_disable in existing code:
>
> Here we do:
> ret = call->class->reg(call, TRACE_REG_REGISTER, file);
>
> But in the error handling path we only do a
> tracing_stop_cmdline_record() and not clear the
> EVENT_FILE_FL_RECORDED_CMD_BIT flag. Is that not an issue? I am
> guessing because enabling of the event itself will fail, that's Ok.
> But just to keep it consistent, I am thinking if we should just clear
> the bit here.
Yeah, we should probably add some better error handling for failed
setting of events. But the tgid-map is low hanging fruit to get
right ;-)
-- Steve
next prev parent reply other threads:[~2017-06-26 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 5:38 [PATCH v4 0/3] " Joel Fernandes
2017-06-26 5:38 ` [PATCH v4 1/3] " Joel Fernandes
2017-06-26 16:52 ` Steven Rostedt
2017-06-26 19:02 ` Joel Fernandes
2017-06-26 19:09 ` Steven Rostedt
2017-06-26 19:10 ` Joel Fernandes
2017-06-26 19:28 ` Steven Rostedt [this message]
2017-06-26 19:12 ` Steven Rostedt
2017-06-26 19:15 ` Joel Fernandes
2017-06-26 5:38 ` [PATCH v4 2/3] tracing: Add support for display of tgid in trace output Joel Fernandes
2017-06-26 5:38 ` [PATCH v4 3/3] tracing/ftrace: Add support to record and display tgid Joel Fernandes
2017-06-27 3:16 ` Joel Fernandes
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=20170626152807.7d40edb7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikesart@gmail.com \
--cc=mingo@redhat.com \
/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®