慕冬亮
unread,Jan 20, 2021, 12:28:17 AM1/20/21Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bri...@redhat.com, ku...@kernel.org, linux-kernel, mi...@kernel.org, pet...@infradead.org, simon....@netronome.com, syzkaller-bugs, syzkaller
Dear kernel developers,
I found that on the syzbot dashboard, “possible deadlock in
static_key_slow_dec” [1] and "possible deadlock in
__static_key_slow_dec" [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 "__static_key_slow_dec";
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 static_key_slow_dec” -
https://syzkaller.appspot.com/bug?id=4671e8c8f5cf5d23a81facabdc4f26ed63f03fc4
[2] “possible deadlock in __static_key_slow_dec” -
https://syzkaller.appspot.com/bug?id=ebc482d3e3ddaa62726a73e0123acef411df13e3
--
My best regards to you.
No System Is Safe!
Dongliang Mu