Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753509AbcKPSc4 (ORCPT <rfc822;w@1wt.eu>);
        Wed, 16 Nov 2016 13:32:56 -0500
Received: from mail-it0-f67.google.com ([209.85.214.67]:34834 "EHLO
        mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751688AbcKPScy (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 16 Nov 2016 13:32:54 -0500
From: Vince Weaver <vincent.weaver@maine.edu>
X-Google-Original-From: Vince Weaver <vince@maine.edu>
Date: Wed, 16 Nov 2016 13:32:51 -0500 (EST)
X-X-Sender: vince@macbook-air
To: Dmitry Vyukov <dvyukov@google.com>
cc: Vince Weaver <vincent.weaver@maine.edu>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Josh Poimboeuf <jpoimboe@redhat.com>, Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        "davej@codemonkey.org.uk" <davej@codemonkey.org.uk>,
        Stephane Eranian <eranian@gmail.com>
Subject: Re: perf: fuzzer KASAN perf_callchain_store on amd
In-Reply-To: <CACT4Y+ZOfMKtW48R3th2KQ+E5xUy9krTfVx5hZ9-mrxTsQdy5Q@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1611161329171.4881@macbook-air>
References: <alpine.DEB.2.20.1611161127170.4881@macbook-air> <CACT4Y+ZOfMKtW48R3th2KQ+E5xUy9krTfVx5hZ9-mrxTsQdy5Q@mail.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
Content-Length: 1285
Lines: 30

On Wed, 16 Nov 2016, Dmitry Vyukov wrote:

> On Wed, Nov 16, 2016 at 5:33 PM, Vince Weaver <vincent.weaver@maine.edu> wrote:
> >
> > [118725.787218]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
> > [118725.793967]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
> > [118725.800690]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
> > [118725.807393]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
> > ...
> 
> 
> This is heap OOB rather than stack OOB.
> Is there an allocation stack/object size/shadow in the report? It
> would greatly help debugging.

No, the report just trailed off and then launched into the next KASAN 
report without anything in between (see below).

I am reporting what was in dmesg, I lost the serial console output.  
I'm currently re-running on the same machine, hopefully I can reproduce it.

[118726.110077]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
[118726.115849]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
[118726.121615]  [<ffffffff811d1512>] ? save_stack+0x33/0xa6
[118726.127385]  [<ffffffff811d

[118726.139200] BAD LUCK: lost 11949 message(s) from NMI context!
[118726.139201] 
==================================================================
[118726.153327] BUG: KASAN: slab-out-of-bounds in perf_callchain_store+0x69/0x84 at addr ffff8801d4fbe800