Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 7 Dec 2020 08:38:24 +0100 (CET)
From:   Richard Weinberger <richard@nod.at>
To:     Boqun Feng <boqun.feng@gmail.com>
Cc:     linux-kernel <linux-kernel@vger.kernel.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Andrey Ryabinin <aryabinin@virtuozzo.com>,
        Alexander Potapenko <glider@google.com>,
        Dmitry Vyukov <dvyukov@google.com>,
        kasan-dev <kasan-dev@googlegroups.com>,
        Peter Zijlstra <peterz@infradead.org>,
        tglx <tglx@linutronix.de>
Message-ID: <1460772961.85699.1607326704865.JavaMail.zimbra@nod.at>
In-Reply-To: <20201207043518.GA1819081@boqun-archlinux>
References: <CAFLxGvwienJ7sU2+QAhFt+ywS9iYkbAXDGviuTC-4CVwLOhXfA@mail.gmail.com> <20201207043518.GA1819081@boqun-archlinux>
Subject: Re: BUG: Invalid wait context with KMEMLEAK and KASAN enabled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Thread-Topic: Invalid wait context with KMEMLEAK and KASAN enabled
Thread-Index: 6g9dKygF4YhpzjznohWxx1ckhTfl2Q==
Precedence: bulk

Boqun,

----- Ursprüngliche Mail -----
>> Does this ring a bell?
>> 
>> [    2.298447] =============================
>> [    2.298971] [ BUG: Invalid wait context ]
>> [    2.298971] 5.10.0-rc6+ #388 Not tainted
>> [    2.298971] -----------------------------
>> [    2.298971] ksoftirqd/1/15 is trying to lock:
>> [    2.298971] ffff888100b94598 (&n->list_lock){....}-{3:3}, at:
>> free_debug_processing+0x3d/0x210
> 
> I guest you also had CONFIG_PROVE_RAW_LOCK_NESTING=y, right?

Yes, this is the case!

Thanks,
//richard