[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230425150349.GG1335080@hirez.programming.kicks-ass.net>
Date: Tue, 25 Apr 2023 17:03:49 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Marco Elver <elver@...gle.com>, Zqiang <qiang1.zhang@...el.com>,
ryabinin.a.a@...il.com, glider@...gle.com, andreyknvl@...il.com,
dvyukov@...gle.com, akpm@...ux-foundation.org,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Qi Zheng <zhengqi.arch@...edance.com>
Subject: Re: [PATCH v2] kasan: Fix lockdep report invalid wait context
On Wed, Apr 19, 2023 at 09:50:23AM +0200, Vlastimil Babka wrote:
> Yes, the problem seems to be that if there's different paths tor RT and !RT
> kernels, PROVE_RAW_LOCK_NESTING doesn't know that and will trigger on the
> !RT path in the !RT kernel. There's was an annotation proposed for these
> cases in the thread linked below, but AFAIK it's not yet finished.
>
> https://lore.kernel.org/all/20230412124735.GE628377@hirez.programming.kicks-ass.net/
Oh, thanks for the reminder, I'd completely forgotten about it. I just
replied with a new version... fingers crossed ;-)
Powered by blists - more mailing lists