public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Hao Sun <sunhao.th@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, a.darwish@linutronix.de,
	johan@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	oneukum@suse.com
Subject: Re: INFO: task hung in hub_port_init
Date: Fri, 17 Sep 2021 22:02:45 -0400	[thread overview]
Message-ID: <20210918020245.GA69263@rowland.harvard.edu> (raw)
In-Reply-To: <CACkBjsZcg0B=tF8cr54VqaJMVURD9R463epZqRQfesnoY=+L8g@mail.gmail.com>

On Sat, Sep 18, 2021 at 09:56:52AM +0800, Hao Sun wrote:
> Hi Alan,
> 
> Alan Stern <stern@rowland.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@gmail.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.

Alan Stern

  reply	other threads:[~2021-09-18  2:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13  3:13 INFO: task hung in hub_port_init Hao Sun
2021-09-13 13:54 ` Alan Stern
2021-09-18  1:56   ` Hao Sun
2021-09-18  2:02     ` Alan Stern [this message]
2021-09-18  2:17       ` Hao Sun
2021-09-18 13:53         ` Alan Stern
2021-09-20 14:31           ` Shuah Khan
2021-09-22 18:15             ` Shuah Khan
  -- strict thread matches above, loose matches on Subject: below --
2020-10-06  8:19 syzbot
2020-10-06  8:56 ` Oliver Neukum
2020-10-06 12:48   ` Andrey Konovalov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210918020245.GA69263@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=a.darwish@linutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=sunhao.th@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox