On Mon, 2020-09-14 at 14:16 -0400, Qian Cai wrote: > On Fri, 2020-08-07 at 15:42 +0800, Boqun Feng wrote: > > Since we have all the fundamental to handle recursive read locks, we now > > add them into the dependency graph. > > > > Signed-off-by: Boqun Feng <boqun.feng@xxxxxxxxx> > > Reverting this patch and its dependency: > > [14/19] lockdep: Take read/write status in consideration when generate > chainkey > > fixed a splat below. IOW, this patch introduced this new splat which looks Sorry, it turned out my previous reproducer was not so reliable, but now I found a new reliable reproducer that could trigger this on both x86 and powerpc every time which so far points out the culprit being the patchset: "[PATCH v1 0/5] seqlock: Introduce PREEMPT_RT support" [1]. It also matched exactly the exact timing (today) between the issue showed up and the patchset was merged into linux-next. I'll do a bit more confirmation and report it there. [1] https://lore.kernel.org/lkml/20200828010710.5407-1-a.darwish@xxxxxxxxxxxxx/
