From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+7a7613e5ba9ae7bd15f9@syzkaller.appspotmail.com>
Cc: bigeasy@linutronix.de, felipe.balbi@linux.intel.com,
gregkh@linuxfoundation.org, joe@perches.com, johan@kernel.org,
kai.heng.feng@canonical.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
rafael.j.wysocki@intel.com, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in usb_bulk_msg
Date: Fri, 28 Aug 2020 16:36:12 +0300 [thread overview]
Message-ID: <20200828133612.GR1891694@smile.fi.intel.com> (raw)
In-Reply-To: <000000000000c69c7805adef8597@google.com>
On Fri, Aug 28, 2020 at 05:52:16AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 15bc20c6 Merge tag 'tty-5.9-rc3' of git://git.kernel.org/p..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1052a669900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=978db74cb30aa994
> dashboard link: https://syzkaller.appspot.com/bug?extid=7a7613e5ba9ae7bd15f9
> compiler: gcc (GCC) 10.1.0-syz 20200507
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101c328e900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=155eff41900000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+7a7613e5ba9ae7bd15f9@syzkaller.appspotmail.com
I have had hard times to understand the link between tty subsystem and this
report. Also I'm wondering how 'Maintainers' column is formed in the dashboard
view. And how the Cc list of this message in particular.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-08-28 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 16:59 INFO: task hung in usb_bulk_msg syzbot
2020-08-28 12:52 ` syzbot
2020-08-28 13:36 ` Andy Shevchenko [this message]
2020-08-29 1:24 ` Alan Stern
2020-08-31 13:08 ` Andrey Konovalov
2020-10-14 16:25 ` Dmitry Vyukov
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=20200828133612.GR1891694@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=johan@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+7a7613e5ba9ae7bd15f9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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