linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+1cb937c125adb93fad2d@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
	gustavo@embeddedor.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in shark_write_val/usb_submit_urb
Date: Fri, 12 May 2023 14:31:34 -0700	[thread overview]
Message-ID: <00000000000047c61c05fb85d44e@google.com> (raw)
In-Reply-To: <000000000000121ea5058e445936@google.com>

syzbot suspects this issue was fixed by commit:

commit 76e31045ba030e94e72105c01b2e98f543d175ac
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Mon Apr 10 19:40:05 2023 +0000

    media: radio-shark: Add endpoint checks

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17cfcfca280000
start commit:   b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=2f98d9171d58550f
dashboard link: https://syzkaller.appspot.com/bug?extid=1cb937c125adb93fad2d
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17070aa6880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=177ab2da880000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: media: radio-shark: Add endpoint checks

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2023-05-12 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 12:38 WARNING in shark_write_val/usb_submit_urb syzbot
2023-05-12 21:31 ` syzbot [this message]
2023-05-13 13:42   ` [syzbot] [usb?] " Alan Stern

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=00000000000047c61c05fb85d44e@google.com \
    --to=syzbot+1cb937c125adb93fad2d@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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).