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 S1752062AbdK3I3Q (ORCPT <rfc822;w@1wt.eu>);
        Thu, 30 Nov 2017 03:29:16 -0500
Received: from mail-pg0-f66.google.com ([74.125.83.66]:38099 "EHLO
        mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750890AbdK3I3P (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 30 Nov 2017 03:29:15 -0500
X-Google-Smtp-Source: AGs4zMbex+Jq0D+19jT6RE2pHfLnNSOiS9KtslGMn/utHsQ5cg+BiJD4fAqHwfjPNqAclX6/S3Cnkw==
Date: Thu, 30 Nov 2017 17:29:09 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Fengguang Wu <fengguang.wu@intel.com>,
        LKML <linux-kernel@vger.kernel.org>, Petr Mladek <pmladek@suse.com>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Ingo Molnar <mingo@kernel.org>,
        Aleksey Makarov <aleksey.makarov@linaro.org>,
        Nicolas Pitre <nicolas.pitre@linaro.org>,
        Nikitas Angelinas <nikitas.angelinas@gmail.com>, LKP <lkp@01.org>,
        kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [ 0.003333] BUG: KASAN: use-after-scope in
 console_unlock+0x605/0xcc0
Message-ID: <20171130082909.GA469@jagdpanzerIV>
References: <20171130022655.2e5ehqmf3lyi4jy3@wfg-t540p.sh.intel.com>
 <20171130064712.GA488@jagdpanzerIV>
 <CACT4Y+amQZApke6MneeK0tax=MzDbj5bce6r4MuSf8PHpzeaoA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACT4Y+amQZApke6MneeK0tax=MzDbj5bce6r4MuSf8PHpzeaoA@mail.gmail.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On (11/30/17 09:16), Dmitry Vyukov wrote:
[..]
> > to be honest, this backtrace hardly makes any sense to me.
> >
> > vprintk_emit()
> >  reserve_standard_io_resources()
> >   __flush_tlb_all()
> >    vprintk_emit()
> >     __down_trylock_console_sem()
> >      wake_up_klogd()
> >       console_unlock()
> >
> > I need some help here.
> 
> 
> You can try dirty patch from here:
> https://groups.google.com/d/msg/kasan-dev/iDb5bhcMBT0/55QzwWaHAwAJ
> It should make KASAN print the exact variable name and frame where it
> was allocated.

would be good if Fengguang can try this out. I can't reproduce the
problem on my x86 box (linux-next and Linus's trees both work fine
for me with KASAN + lockdep + TRACE_IRQ).

	-ss