From: Steven Rostedt <rostedt@goodmis.org>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@lists.01.org
Subject: Re: [tracing] 06e0a548ba: WARNING:at_kernel/trace/ring_buffer.c:#ring_buffer_iter_peek
Date: Wed, 13 May 2020 09:29:22 -0400 [thread overview]
Message-ID: <20200513092922.6d79f6ee@gandalf.local.home> (raw)
In-Reply-To: <20200513091906.GA12720@tuxmaker.boeblingen.de.ibm.com>
On Wed, 13 May 2020 11:19:06 +0200
Sven Schnelle <svens@linux.ibm.com> wrote:
> Did you had a chance to look into this? I can easily reproduce this both on x86
> and s390 by doing:
>
> cd /sys/kernel/tracing
> cat /dev/zero >/dev/null & # generate some load
> echo function >current_tracer
> # wait a few seconds to fill the buffer
> cat trace
>
> Usually it will print the warn after a few seconds.
>
> I haven't digged through all the ring buffer code yet, so i thought i might ask
> whether you have an idea what's going on.
Can you send me the config for where you can reproduce it on x86?
The iterator now doesn't stop the ring buffer when it iterates, and is
doing so over a live buffer (but should be able to handle it). It's
triggering something I thought wasn't suppose to happen (which must be
happening).
Perhaps with your config I'd be able to reproduce it.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: lkp@lists.01.org
Subject: Re: [tracing] 06e0a548ba: WARNING:at_kernel/trace/ring_buffer.c:#ring_buffer_iter_peek
Date: Wed, 13 May 2020 09:29:22 -0400 [thread overview]
Message-ID: <20200513092922.6d79f6ee@gandalf.local.home> (raw)
In-Reply-To: <20200513091906.GA12720@tuxmaker.boeblingen.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
On Wed, 13 May 2020 11:19:06 +0200
Sven Schnelle <svens@linux.ibm.com> wrote:
> Did you had a chance to look into this? I can easily reproduce this both on x86
> and s390 by doing:
>
> cd /sys/kernel/tracing
> cat /dev/zero >/dev/null & # generate some load
> echo function >current_tracer
> # wait a few seconds to fill the buffer
> cat trace
>
> Usually it will print the warn after a few seconds.
>
> I haven't digged through all the ring buffer code yet, so i thought i might ask
> whether you have an idea what's going on.
Can you send me the config for where you can reproduce it on x86?
The iterator now doesn't stop the ring buffer when it iterates, and is
doing so over a live buffer (but should be able to handle it). It's
triggering something I thought wasn't suppose to happen (which must be
happening).
Perhaps with your config I'd be able to reproduce it.
-- Steve
next prev parent reply other threads:[~2020-05-13 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:05 [tracing] 06e0a548ba: WARNING:at_kernel/trace/ring_buffer.c:#ring_buffer_iter_peek kernel test robot
2020-04-29 9:05 ` kernel test robot
2020-05-13 9:19 ` Sven Schnelle
2020-05-13 13:29 ` Steven Rostedt [this message]
2020-05-13 13:29 ` Steven Rostedt
2020-05-13 16:15 ` Sven Schnelle
2020-05-13 16:25 ` Steven Rostedt
2020-05-13 16:25 ` Steven Rostedt
2020-05-13 19:30 ` Steven Rostedt
2020-05-13 19:30 ` Steven Rostedt
2020-05-14 6:09 ` Sven Schnelle
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=20200513092922.6d79f6ee@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.