Closed cpaasch closed 1 year ago
I can't understand this stack trace: there is only one sk_clone_lock() call in it, I don't see how that could trigger a recursive lock?!? Unless there is some prior data corruption (kasan is not enabled, could possibly go unnoticed until too late) confusing lockdep.
Some notes from the meeting of the 12th of september:
this really looks like a duplicate of #447
syzkaller-id: 664c5311cf44e3aa732eaa6b2e79eb4a8961ec08
HEAD: 2227de86e754
Trace:
No reproducer
Kconfig: Kconfig_k5_lockdep.txt