From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/7] trace-cmd: Fixed logic in tracecmd_read_page_record()
Date: Fri, 8 Feb 2019 17:08:38 -0500 [thread overview]
Message-ID: <20190208170838.5f0faa1f@gandalf.local.home> (raw)
In-Reply-To: <20190208134918.5618-4-tstoyanov@vmware.com>
On Fri, 8 Feb 2019 15:49:14 +0200
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
> Fixed the logic in tracecmd_read_page_record() when
> searching for the next event in the event from the
> ring buffer. In the current logic, in the case when
> last_record is not NULL (we are searching for the second one)
> the check "if (ptr != last_record->data)" always fails.
>
Nice catch.
Let's change the change log and subject:
Subject trace-cmd: Fix tracecmd_read_page_record() to read more than one event
The kbuffer_next_event() will return the next event on the sub buffer.
If we pass in the last_record to tracecmd_read_page_record(), it
initializes the sub buffer, and by calling kbuffer_next_event()
(instead of kbuffer_read_event()), the second event on the sub buffer
is returned. This causes the match of the last_record not to match if
the last_record happens to be the first event on the sub buffer.
> Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> ---
> lib/trace-cmd/trace-input.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/lib/trace-cmd/trace-input.c b/lib/trace-cmd/trace-input.c
> index 33ad7d1..5d64ca8 100644
> --- a/lib/trace-cmd/trace-input.c
> +++ b/lib/trace-cmd/trace-input.c
> @@ -1688,18 +1688,22 @@ tracecmd_read_page_record(struct tep_handle *pevent, void *page, int size,
> goto out_free;
> }
>
> - do {
> + ptr = kbuffer_read_event(kbuf, &ts);
> + while (ptr < last_record->data) {
> ptr = kbuffer_next_event(kbuf, NULL);
> if (!ptr)
> break;
> - } while (ptr < last_record->data);
> + if (ptr == last_record->data)
> + break;
> + }
> if (ptr != last_record->data) {
> warning("tracecmd_read_page_record: could not find last_record");
> goto out_free;
> }
> - }
> + ptr = kbuffer_next_event(kbuf, &ts);
> + } else
> + ptr = kbuffer_read_event(kbuf, &ts);
>
> - ptr = kbuffer_read_event(kbuf, &ts);
Also, instead of the above "} else" clause, we can just move the
ptr = kbuffer_read_event(kbuf, &ts);
before the if condition testing last_record.
-- Steve
> if (!ptr)
> goto out_free;
>
next prev parent reply other threads:[~2019-02-08 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 13:49 [PATCH v3 0/7][POC] trace-cmd: Timetamps sync using PTP-like algorithm, relying on vsock events Tzvetomir Stoyanov
2019-02-08 13:49 ` [PATCH v3 1/7] trace-cmd: Implemented new lib API: tracecmd_local_events_system() Tzvetomir Stoyanov
2019-02-08 13:49 ` [PATCH v3 2/7] trace-cmd: Added support for negative time offsets in trace.dat file Tzvetomir Stoyanov
2019-02-08 21:39 ` Steven Rostedt
2019-02-08 13:49 ` [PATCH v3 3/7] trace-cmd: Fixed logic in tracecmd_read_page_record() Tzvetomir Stoyanov
2019-02-08 22:08 ` Steven Rostedt [this message]
2019-02-08 13:49 ` [PATCH v3 4/7] trace-cmd: Added implementation of htonll() and ntohll() Tzvetomir Stoyanov
2019-02-08 13:49 ` [PATCH v3 5/7] trace-cmd: Refactored make_instances() and tracecmd_remove_instances() Tzvetomir Stoyanov
2019-02-08 22:11 ` Steven Rostedt
2019-02-08 22:44 ` Steven Rostedt
2019-02-08 22:46 ` Steven Rostedt
2019-02-08 13:49 ` [PATCH v3 6/7] trace-cmd: Find and store pids of tasks, which run virtual CPUs of given VM Tzvetomir Stoyanov
2019-02-08 13:49 ` [PATCH v3 7/7] trace-cmd [POC]: Implemented timestamps synch PTP-like algorithm, using vsock events Tzvetomir Stoyanov
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=20190208170838.5f0faa1f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@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).