From: Joel Fernandes <joel@joelfernandes.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] [tracing] c3bc8fd637: WARNING:at_kernel/rcu/tree.c:#rcu_irq_enter
Date: Tue, 28 Aug 2018 12:53:47 -0700 [thread overview]
Message-ID: <20180828195347.GA228832@joelaf.mtv.corp.google.com> (raw)
In-Reply-To: <20180823023839.GA13343@shao2-debian>
On Thu, Aug 23, 2018 at 10:38:39AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: c3bc8fd637a9623f5c507bd18f9677effbddf584 ("tracing: Centralize preemptirq tracepoints and unify their usage")
> https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git ftrace/core
>
> in testcase: trinity
> with following parameters:
>
> runtime: 300s
>
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/
This appears to not be testing the tip of ftrace/core or Linus's tree which
contains several other patches/fixes ontop.
thanks,
- Joel
next prev parent reply other threads:[~2018-08-28 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 2:38 kernel test robot
2018-08-28 19:53 ` Joel Fernandes [this message]
2020-09-25 4:43 ` [stable 4.19] [PANIC]: tracing: Centralize preemptirq tracepoints and unify their usage Naresh Kamboju
2020-09-25 5:15 ` Greg Kroah-Hartman
2020-09-25 7:25 ` Naresh Kamboju
2020-09-25 14:54 ` Steven Rostedt
2020-09-25 14:59 ` Steven Rostedt
2020-09-25 15:07 ` Steven Rostedt
2020-09-25 15:12 ` Greg Kroah-Hartman
2020-09-25 15:30 ` Steven Rostedt
2020-10-05 13:18 ` Greg Kroah-Hartman
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=20180828195347.GA228832@joelaf.mtv.corp.google.com \
--to=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rong.a.chen@intel.com \
--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®