Dear kernel developers, I found that on the syzbot dashboard, “possible deadlock in console_lock_spinning_enable”[1] and "possible deadlock in console_unlock"[2] should share the same root cause.
The reasons for the above statement: 1) the stack trace is the same, and this title difference is due to the inline property of "console_lock_spinning_enable"; 2) their PoCs are the same as each other; If you can have any issues with this statement or our information is useful to you, please let us know. Thanks very much. [1] “possible deadlock in console_lock_spinning_enable” - https://syzkaller.appspot.com/bug?id=2820deb61d92a8d7ab17a56ced58e963e65d76d0 [2] “possible deadlock in console_unlock” - https://syzkaller.appspot.com/bug?id=39ea6caa479af471183997376dc7e90bc7d64a6a -- My best regards to you. No System Is Safe! Dongliang Mu
