linux-kernel - Re: "possible deadlock in console_lock_spinning_enable" and "possible deadlock in console_unlock" should be duplicate crash behaviors

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 21 Jan 2021 09:17:27 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     慕冬亮 <mudongliangabcd@...il.com>
Cc:     jirislaby@...nel.org, linux-kernel <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: "possible deadlock in console_lock_spinning_enable" and
 "possible deadlock in console_unlock" should be duplicate crash behaviors

On Thu, Jan 21, 2021 at 01:37:05PM +0800, 慕冬亮 wrote:
> 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

Any proposed patch for these issues?

thanks,

greg k-h