From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <ykaradzhov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] kernel-shark-qt: Fix bug in plugin actions execution
Date: Thu, 14 Mar 2019 20:01:14 -0400 [thread overview]
Message-ID: <20190314200114.4c5abf5b@gandalf.local.home> (raw)
In-Reply-To: <20190109115253.70c0bc18@gandalf.local.home>
Ping?
-- Steve
On Wed, 9 Jan 2019 11:52:53 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 9 Jan 2019 15:09:45 +0200
> Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
>
> > Plugin-provided actions are executed when loading the data. These
> > actions can be used to modify the contain of the kshark_entries
>
> "modify the contain of" ?
>
> > generated by a given event type and we consider the case of having
> > more than one plugin-provided actions per event type. However, the code
>
> "more than one plugin-provided actions per event type." also doesn't
> make sense.
>
> > that handles the case of multiple actions per-event has a bug. The "if"
> > was introduced with the idea that only the last per-event action will
> > modify the KS_PLUGIN_UNTOUCHED flag of the entry, but it misbehaves in
> > the case of a single per-event action in the list, followed by actions
> > for other events.
>
> Patch looks fine, but can you resend with a cleaner change log?
>
> Thanks!
>
> -- Steve
>
> >
> > Signed-off-by: Yordan Karadzhov <ykaradzhov@vmware.com>
> > ---
> > kernel-shark-qt/src/libkshark.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/kernel-shark-qt/src/libkshark.c b/kernel-shark-qt/src/libkshark.c
> > index 598ea52..9ab2d57 100644
> > --- a/kernel-shark-qt/src/libkshark.c
> > +++ b/kernel-shark-qt/src/libkshark.c
> > @@ -750,8 +750,7 @@ static size_t get_records(struct kshark_context *kshark_ctx,
> > entry->event_id))) {
> > evt_handler->event_func(kshark_ctx, rec, entry);
> > evt_handler = evt_handler->next;
> > - if (!evt_handler)
> > - entry->visible &= ~KS_PLUGIN_UNTOUCHED_MASK;
> > + entry->visible &= ~KS_PLUGIN_UNTOUCHED_MASK;
> > }
> >
> > pid = entry->pid;
>
next prev parent reply other threads:[~2019-03-15 0:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 13:09 [PATCH v2 0/6] Modifications toward KS 1.0 Yordan Karadzhov
2019-01-09 13:09 ` [PATCH v2 1/6] kernel-shark-qt: Rearrange the "Filter" top menu Yordan Karadzhov
2019-01-09 13:09 ` [PATCH v2 2/6] kernel-shark-qt: Cosmetic modifications in KsQuickContextMenu Yordan Karadzhov
2019-01-09 16:33 ` Steven Rostedt
2019-01-09 16:38 ` Yordan Karadzhov
2019-01-09 16:47 ` Steven Rostedt
2019-01-09 13:09 ` [PATCH v2 3/6] kernel-shark-qt: Make the selection in the Table less touchy Yordan Karadzhov
2019-01-09 13:09 ` [PATCH v2 4/6] kernel-shark-qt: Do not auto-scrolling when the marker switches Yordan Karadzhov
2019-01-09 13:09 ` [PATCH v2 5/6] kernel-shark-qt: Add the CPU filters to the filter clearing method Yordan Karadzhov
2019-01-09 13:09 ` [PATCH v2 6/6] kernel-shark-qt: Fix bug in plugin actions execution Yordan Karadzhov
2019-01-09 16:52 ` Steven Rostedt
2019-03-15 0:01 ` Steven Rostedt [this message]
2019-03-15 0:05 ` Steven Rostedt
2019-03-15 6:20 ` Yordan Karadzhov
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=20190314200114.4c5abf5b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=ykaradzhov@vmware.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;
as well as URLs for NNTP newsgroup(s).