netdev - "WARNING: locking bug in finish_task_switch" and "WARNING: locking bug in finish_lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAD-N9QVWNK=SPgT0mc81_UqbSV57aQ+x-s=iz9PnjQWNc5bG6A@mail.gmail.com>
Date:   Wed, 20 Jan 2021 13:03:52 +0800
From:   慕冬亮 <mudongliangabcd@...il.com>
To:     davem@...emloft.net, johan.hedberg@...il.com, kuba@...nel.org,
        linux-bluetooth@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>, marcel@...tmann.org,
        netdev@...r.kernel.org,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        syzkaller <syzkaller@...glegroups.com>
Subject: "WARNING: locking bug in finish_task_switch" and "WARNING: locking
 bug in finish_lock_switch" should share the same root cause

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