From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753238AbaEAGvQ (ORCPT ); Thu, 1 May 2014 02:51:16 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:32891 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751261AbaEAGvP (ORCPT ); Thu, 1 May 2014 02:51:15 -0400 Date: Thu, 1 May 2014 08:51:05 +0200 From: Peter Zijlstra To: Sasha Levin Cc: paulus@samba.org, Ingo Molnar , acme@ghostprotocols.net, LKML , Dave Jones Subject: Re: perf: memory corruption in perf_event_mmap Message-ID: <20140501065105.GJ11096@twins.programming.kicks-ass.net> References: <5361758D.3090005@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5361758D.3090005@oracle.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 :/