linux-kernel - "INFO: task hung in exit_mm" and "INFO: task hung in do

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-N9QXHkGkwihX=E7HAnDs3L90=Q5FerLb0mJhdXMb+pH-tew@mail.gmail.com>
Date:   Thu, 21 Jan 2021 13:58:58 +0800
From:   慕冬亮 <mudongliangabcd@...il.com>
To:     aarcange@...hat.com, akpm@...ux-foundation.org, avagin@...il.com,
        davem@...emloft.net, ebiederm@...ssion.com,
        linux-kernel <linux-kernel@...r.kernel.org>, oleg@...hat.com,
        prsood@...eaurora.org, tj@...nel.org
Cc:     syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        syzkaller <syzkaller@...glegroups.com>
Subject: "INFO: task hung in exit_mm" and "INFO: task hung in do_exit" should
 be duplicate crash reports

Dear kernel developers,

I found that on the syzbot dashboard, “INFO: task hung in exit_mm”[1]
and "INFO: task hung in do_exit"[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 "exit_mm";
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] “INFO: task hung in exit_mm” -
https://syzkaller.appspot.com/bug?id=dd115babf1498c3370fab8758d58940b7c6bffa4

[2] “INFO: task hung in do_exit” -
https://syzkaller.appspot.com/bug?id=3e6c42e24155e5f0125368e609bee32f2b7394fe

--
My best regards to you.

     No System Is Safe!
     Dongliang Mu