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 S970905AbdAEOtx (ORCPT <rfc822;w@1wt.eu>);
        Thu, 5 Jan 2017 09:49:53 -0500
Received: from mx1.redhat.com ([209.132.183.28]:36688 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S966758AbdAEOtp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 5 Jan 2017 09:49:45 -0500
Date: Thu, 5 Jan 2017 08:49:42 -0600
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrey Konovalov <andreyknvl@google.com>,
        syzkaller <syzkaller@googlegroups.com>,
        Andrey Ryabinin <aryabinin@virtuozzo.com>,
        Alexander Potapenko <glider@google.com>,
        kasan-dev <kasan-dev@googlegroups.com>,
        "linux-mm@kvack.org" <linux-mm@kvack.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>, "x86@kernel.org" <x86@kernel.org>,
        Kostya Serebryany <kcc@google.com>
Subject: Re: x86: warning in unwind_get_return_address
Message-ID: <20170105144942.whqucdwmeqybng3s@treble>
References: <CAAeHK+yqC-S=fQozuBF4xu+d+e=ikwc_ipn-xUGnmfnWsjUtoA@mail.gmail.com>
 <20161220210144.u47znzx6qniecuvv@treble>
 <CAAeHK+z7O-byXDL4AMZP5TdeWHSbY-K69cbN6EeYo5eAtvJ0ng@mail.gmail.com>
 <20161220233640.pc4goscldmpkvtqa@treble>
 <CAAeHK+yPSeO2PWQtsQs_7FQ0PeGzs4PgK_89UM8G=hFJrVzH1g@mail.gmail.com>
 <20161222051701.soqwh47frxwsbkni@treble>
 <CACT4Y+ZxTLcpwQOBCyMZGFuXeDrbu9-RBaqzgnE57UPeDSPE+g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CACT4Y+ZxTLcpwQOBCyMZGFuXeDrbu9-RBaqzgnE57UPeDSPE+g@mail.gmail.com>
User-Agent: Mutt/1.6.0.1 (2016-04-01)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Thu, 05 Jan 2017 14:49:46 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Dec 27, 2016 at 05:38:59PM +0100, Dmitry Vyukov wrote:
> On Thu, Dec 22, 2016 at 6:17 AM, Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> > On Wed, Dec 21, 2016 at 01:46:36PM +0100, Andrey Konovalov wrote:
> >> On Wed, Dec 21, 2016 at 12:36 AM, Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> >> >
> >> > Thanks.  Looking at the stack trace, my guess is that an interrupt hit
> >> > while running in generated BPF code, and the unwinder got confused
> >> > because regs->ip points to the generated code.  I may need to disable
> >> > that warning until we figure out a better solution.
> >> >
> >> > Can you share your .config file?
> >>
> >> Sure, attached.
> >
> > Ok, I was able to recreate with your config.  The culprit was generated
> > code, as I suspected, though it wasn't BPF, it was a kprobe (created by
> > dccpprobe_init()).
> >
> > I'll make a patch to disable the warning.
> 
> Hi,
> 
> I am also seeing the following warnings:
> 
> [  281.889259] WARNING: kernel stack regs at ffff8801c29a7ea8 in
> syz-executor8:1302 has bad 'bp' value ffff8801c29a7f28
> [  833.994878] WARNING: kernel stack regs at ffff8801c4e77ea8 in
> syz-executor1:13094 has bad 'bp' value ffff8801c4e77f28
> 
> Can it also be caused by bpf/kprobe?

This is a different warning.  I suspect it's due to unwinding the stack
of another CPU while it's running, which is still possible in a few
places.  I'm going to have to disable all these warnings for now.

-- 
Josh