From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755800AbcHXNUd (ORCPT <rfc822;w@1wt.eu>);
        Wed, 24 Aug 2016 09:20:33 -0400
Received: from mail-it0-f41.google.com ([209.85.214.41]:34880 "EHLO
        mail-it0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932372AbcHXNUa (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 Aug 2016 09:20:30 -0400
From: Vince Weaver <vincent.weaver@maine.edu>
X-Google-Original-From: Vince Weaver <vince@maine.edu>
Date: Wed, 24 Aug 2016 09:20:24 -0400 (EDT)
X-X-Sender: vince@macbook-air
To: Ingo Molnar <mingo@kernel.org>
cc: Vince Weaver <vincent.weaver@maine.edu>,
        Peter Zijlstra <peterz@infradead.org>, Huang Rui <ray.huang@amd.com>,
        linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
        Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: fuzzer crashes immediately on AMD system
In-Reply-To: <20160824091923.GB4340@gmail.com>
Message-ID: <alpine.DEB.2.20.1608240917580.2070@macbook-air>
References: <alpine.DEB.2.20.1608181025160.19862@macbook-air> <alpine.DEB.2.20.1608181046120.19862@macbook-air> <20160819100130.GD10121@twins.programming.kicks-ass.net> <20160822111631.GA25844@hr-amur2> <alpine.DEB.2.20.1608222057360.29115@macbook-air>
 <alpine.DEB.2.20.1608222250120.29115@macbook-air> <20160823084519.GN10153@twins.programming.kicks-ass.net> <alpine.DEB.2.20.1608230750310.30245@macbook-air> <20160824091923.GB4340@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 24 Aug 2016, Ingo Molnar wrote:
> If there's no progress finding the root cause I'd be happy to exchange a crash for 
> a leak ...

It's actually a crash of the program doing the perf_event_open() call, not 
a crash of the system (at least in my experience).

However, it's possible that if you have bad luck and if the kfree'd space 
is reused with just the right combination of values you could potentially 
end up crashing the system.

Vince