From: Alan Stern <stern@rowland.harvard.edu>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+9b57a46bf1801ce2a2ca@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in hid_submit_ctrl/usb_submit_urb
Date: Wed, 18 Aug 2021 15:01:25 -0400 [thread overview]
Message-ID: <20210818190125.GE197200@rowland.harvard.edu> (raw)
In-Reply-To: <00000000000038c55d05c9d1dc3b@google.com>
On Wed, Aug 18, 2021 at 02:14:23AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 794c7931a242 Merge branch 'linus' of git://git.kernel.org/..
> git tree: upstream
Dmitry:
Why does syzbot persist in reporting useless names like "upstream" for
the git tree being tested? How is anyone supposed to know what that
actually refers to? Why doesn't it put the real name (maybe with
"upstream" in parentheses as an additional comment)?
Furthermore, the last time I tried to submit a test patch with something
like "#syz test: upstream 794c7931a242", it didn't work because syzbot
itself didn't recognize the repository name!
This should already be fixed -- I can't remember when I first reported
the problem but it must have been at least two years ago.
If there isn't already a change request pending for this issue, can you
add one?
Thanks,
Alan Stern
next prev parent reply other threads:[~2021-08-18 19:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 15:46 [syzbot] WARNING in hid_submit_ctrl/usb_submit_urb syzbot
2021-08-18 9:14 ` syzbot
2021-08-18 18:49 ` Alan Stern
2021-08-18 20:13 ` syzbot
2021-08-19 15:26 ` Alan Stern
2021-08-19 17:35 ` syzbot
2021-08-19 19:53 ` Alan Stern
2021-08-20 0:40 ` syzbot
2021-08-20 14:06 ` Alan Stern
2021-08-24 11:53 ` Jiri Kosina
2021-08-24 12:34 ` Benjamin Tissoires
2021-08-31 9:51 ` Benjamin Tissoires
2021-08-31 13:34 ` Alan Stern
2021-08-31 19:53 ` Jiri Kosina
2021-09-01 15:38 ` Alan Stern
2021-09-01 15:51 ` Michal Kubecek
2021-08-24 11:50 ` Michal Kubecek
2021-08-30 19:22 ` Oleksandr Natalenko
2021-08-18 19:01 ` Alan Stern [this message]
2021-08-18 19:39 ` syzbot
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=20210818190125.GE197200@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+9b57a46bf1801ce2a2ca@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;
as well as URLs for NNTP newsgroup(s).