linux-kernel - "possible deadlock in static_key_slow_dec" and "possible deadlock in __static_key_slow

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-N9QWyfAgVRcgOoWtR87_VqYvMNZxxBpFSxYQ+ME7tEHv_Rw@mail.gmail.com>
Date:   Wed, 20 Jan 2021 13:27:49 +0800
From:   慕冬亮 <mudongliangabcd@...il.com>
To:     bristot@...hat.com, kuba@...nel.org,
        linux-kernel <linux-kernel@...r.kernel.org>, mingo@...nel.org,
        peterz@...radead.org, simon.horman@...ronome.com,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        syzkaller <syzkaller@...glegroups.com>
Subject: "possible deadlock in static_key_slow_dec" and "possible deadlock in
 __static_key_slow_dec" should share the same root cause

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