From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf, kprobes: fuzzer generates huge number of WARNings
Date: Tue, 07 Jul 2015 19:35:20 +0900 [thread overview]
Message-ID: <559BAB68.9000009@hitachi.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1507062355140.26330@vincent-weaver-1.umelst.maine.edu>
On 2015/07/07 13:00, Vince Weaver wrote:
> On Tue, 7 Jul 2015, Masami Hiramatsu wrote:
>
>> On 2015/07/07 6:27, Vince Weaver wrote:
>>> Hello
>>>
>>> I've been working on trying to get the perf_fuzzer to start fuzzing the
>>> PERF_EVENT_IOC_SET_BPF so I've added some really hackish kprobe support.
>>>
>>> However before I can get to the BPF testing the kprobe code generates a
>>> constant stream of WARNINGS which make the machine more or less useless
>>> until I stop it. I've included a small selection here.
>>>
>>> Is this expected?
>>
>> Did you get same message without BPF hack? And also, could you tell us
>> your kernel version and configuration?
>
> It's a Hawell machine running 4.2-rc1. I can post the .config if it's of
> interest.
Yes, I'm interested in.
> Well the BPF hack is in the fuzzer, not the kernel. And it's not really a
> hack, it just turned out to be a huge pain to figure out how to
> manually create a valid BPF program in conjunction with a valid kprobe
> event.
>
> I did have to sprinkle printks in the kprobe and bpf code to find out
> where various EINVAL returns were coming from, so potentially this is just
> a problem of printks happening where they shouldn't. I'll remove those
> changes and try to reproduce this tomorrow.
OK, and also, if you have a chance, please run the ftracetest as below.
$ cd tools/testing/selftest/ftrace/
$ sudo ./ftracetest
This will do a series of basic tests on ftrace and report it.
> This is possibly a long standing issue, until now I never ran the fuzzer
> as root so these particular code paths weren't tested.
Thanks,
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-07-07 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 21:27 Vince Weaver
2015-07-06 21:29 ` Steven Rostedt
2015-07-07 3:53 ` Vince Weaver
2015-07-07 2:25 ` Masami Hiramatsu
2015-07-07 4:00 ` Vince Weaver
2015-07-07 10:35 ` Masami Hiramatsu [this message]
2015-07-07 15:06 ` Vince Weaver
2015-07-07 15:10 ` Steven Rostedt
2015-07-07 18:06 ` Vince Weaver
2015-07-08 3:13 ` Masami Hiramatsu
2015-07-07 15:11 ` Vince Weaver
2015-07-09 9:58 ` Masami Hiramatsu
2015-07-07 19:18 ` Alexei Starovoitov
2015-07-07 21:08 ` Vince Weaver
2015-07-07 21:21 ` Alexei Starovoitov
2015-07-08 13:11 ` Masami Hiramatsu
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=559BAB68.9000009@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.weaver@maine.edu \
/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
Powered by JetHome