From: Thomas Gleixner <tglx@linutronix.de>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf_fuzzer: BUG in kfree() in ftrace_graph_exit_task
Date: Mon, 31 Mar 2014 18:32:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1403311826280.14882@ionos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1403311207490.8953@vincent-weaver-1.um.maine.edu>
On Mon, 31 Mar 2014, Vince Weaver wrote:
>
> This turned up with the perf_fuzzer, haswell, 3.14.
>
> I'm not sure if this is related to the other object corruption bug I am
> seeing. The sympstoms are similar (BUG when dereferencing low invalid
> kernel address) but this time the hrtimer code is not involved at all.
>
> This isn't reproducible, that is if I re-run the fuzzer with the same
> random seed after reboot the bug doesn't trigger.
>
>
> [ 5498.573458] BUG: unable to handle kernel NULL pointer dereference at 000000000000006c
> [ 5498.585181] IP: [<ffffffff81189111>] kfree+0x91/0x220
> [ 5498.593887] PGD 0
> [ 5498.599365] Oops: 0000 [#1] SMP
> [ 5498.606127] Dumping ftrace buffer:
> [ 5498.612973] (ftrace buffer empty)
> [ 5498.619868] Modules linked in: nfsd auth_rpcgss .....
> [ 5498.720303] CPU: 1 PID: 13 Comm: ksoftirqd/1 Tainted: G W 3.14.0+ #14
It's already tainted with W, so there was a warning before that
crash. It would be interesting to see that as well.
Thanks,
tglx
next prev parent reply other threads:[~2014-03-31 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 16:23 Vince Weaver
2014-03-31 16:32 ` Thomas Gleixner [this message]
2014-03-31 16:47 ` Steven Rostedt
2014-03-31 17:04 ` Vince Weaver
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=alpine.DEB.2.02.1403311826280.14882@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®