linux-kernel - Re: INFO: task hung in hub_port

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]

Message-ID: <CACkBjsZPjO96NzLjKR2N7bYzBJRN6sPuaDpK6cvmGqKTd=Byow@mail.gmail.com>
Date:   Sat, 18 Sep 2021 10:17:26 +0800
From:   Hao Sun <sunhao.th@...il.com>
To:     Alan Stern <stern@...land.harvard.edu>
Cc:     Greg KH <gregkh@...uxfoundation.org>, linux-usb@...r.kernel.org,
        a.darwish@...utronix.de, johan@...nel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        oneukum@...e.com
Subject: Re: INFO: task hung in hub_port_init

Alan Stern <stern@...land.harvard.edu> 于2021年9月18日周六 上午10:02写道：
>
> On Sat, Sep 18, 2021 at 09:56:52AM +0800, Hao Sun wrote:
> > Hi Alan,
> >
> > Alan Stern <stern@...land.harvard.edu> 于2021年9月13日周一 下午9:55写道：
> > >
> > > On Mon, Sep 13, 2021 at 11:13:15AM +0800, Hao Sun wrote:
> > > > Hello,
> > > >
> > > > When using Healer to fuzz the Linux kernel, the following crash was triggered.
> > > >
> > > > HEAD commit: ac08b1c68d1b Merge tag 'pci-v5.15-changes'
> > > > git tree: upstream
> > > > console output:
> > > > https://drive.google.com/file/d/1ZeDIMe-DoY3fB32j2p5ifgpq-Lc5N74I/view?usp=sharing
> > > > kernel config: https://drive.google.com/file/d/1qrJUXD8ZIeAkg-xojzDpp04v9MtQ8RR6/view?usp=sharing
> > > > Syzlang reproducer:
> > > > https://drive.google.com/file/d/1tZe8VmXfxoPqlNpzpGOd-e5WCSWgbkxB/view?usp=sharing
> > > > Similar report:
> > > > https://groups.google.com/g/syzkaller-bugs/c/zX55CUzjBOY/m/uf91r0XqAgAJ
> > > >
> > > > Sorry, I don't have a C reproducer for this crash but have a Syzlang
> > > > reproducer. Also, hope the symbolized report can help.
> > > > Here are the instructions on how to execute Syzlang prog:
> > > > https://github.com/google/syzkaller/blob/master/docs/executing_syzkaller_programs.md
> > > >
> > > > If you fix this issue, please add the following tag to the commit:
> > > > Reported-by: Hao Sun <sunhao.th@...il.com>
> > >
> > > There's not much hope of finding the cause of a problem like this
> > > without seeing the kernel log.
> > >
> >
> > Healer found another Syzlang prog to reproduce this task hang:
> > https://paste.ubuntu.com/p/HCNYbKJYtx/
> >
> > Also here is a very simple script to execute the reproducer:
> > https://paste.ubuntu.com/p/ZTGmvFSP6d/
> >
> > The `syz-execprog` and `syz-executor` are needed, so please build
> > Syzkaller first before running the script.
> > Hope this can help to find the root cause of the problem.
>
> I don't have time to install and figure out how to use Healer and
> Syzkaller.  But if you run the reproducer and post the kernel log,
> I'll take a look at it.
>

Just executed the reproducer, here is the full log:
https://paste.ubuntu.com/p/x43SqQy8PX/

Hao