[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161222051701.soqwh47frxwsbkni@treble>
Date: Wed, 21 Dec 2016 23:17:01 -0600
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Andrey Konovalov <andreyknvl@...gle.com>
Cc: syzkaller <syzkaller@...glegroups.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Kostya Serebryany <kcc@...gle.com>
Subject: Re: x86: warning in unwind_get_return_address
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@...hat.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.
--
Josh
Powered by blists - more mailing lists