* "WARNING: locking bug in finish_task_switch" and "WARNING: locking bug in finish_lock_switch" should share the same root cause
@ 2021-01-20 5:03 慕冬亮
0 siblings, 0 replies; only message in thread
From: 慕冬亮 @ 2021-01-20 5:03 UTC (permalink / raw)
To: davem, johan.hedberg, kuba, linux-bluetooth, linux-kernel,
marcel, netdev, syzkaller-bugs, syzkaller
Dear kernel developers,
I found that on the syzbot dashboard, “WARNING: locking bug in
finish_task_switch”[1] and
"WARNING: locking bug in finish_lock_switch"[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 "finish_lock_switch";
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] WARNING: locking bug in finish_task_switch -
https://syzkaller.appspot.com/bug?id=fff3de4144dc949f632cb91af9b12f9c2f309894
[2] WARNING: locking bug in finish_lock_switch -
https://syzkaller.appspot.com/bug?id=c7f3ee17ec2ac6f27e0c72f2a90eabc3c4e1d998
--
My best regards to you.
No System Is Safe!
Dongliang Mu
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-01-20 5:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-20 5:03 "WARNING: locking bug in finish_task_switch" and "WARNING: locking bug in finish_lock_switch" should share the same root cause 慕冬亮
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).