From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: paulus@samba.org, Ingo Molnar <mingo@kernel.org>,
acme@ghostprotocols.net, LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: perf: memory corruption in perf_event_mmap
Date: Thu, 1 May 2014 08:51:05 +0200 [thread overview]
Message-ID: <20140501065105.GJ11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <5361758D.3090005@oracle.com>
On Wed, Apr 30, 2014 at 06:13:33PM -0400, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel I've stumbled on the following:
We are currently chasing memory corruption. Hard to say if its the same
or not :/
next prev parent reply other threads:[~2014-05-01 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 22:13 perf: memory corruption in perf_event_mmap Sasha Levin
2014-05-01 6:51 ` Peter Zijlstra [this message]
2014-05-07 15:54 ` Sasha Levin
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=20140501065105.GJ11096@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=sasha.levin@oracle.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