[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1460772961.85699.1607326704865.JavaMail.zimbra@nod.at>
Date: Mon, 7 Dec 2020 08:38:24 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Boqun Feng <boqun.feng@...il.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>,
Peter Zijlstra <peterz@...radead.org>,
tglx <tglx@...utronix.de>
Subject: Re: BUG: Invalid wait context with KMEMLEAK and KASAN enabled
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
Powered by blists - more mailing lists