mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: syzbot <syzbot+1cb937c125adb93fad2d@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, gregkh@linuxfoundation.org,
	gustavo@embeddedor.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in shark_write_val/usb_submit_urb
Date: Sat, 13 May 2023 09:42:39 -0400	[thread overview]
Message-ID: <bc3011b3-e742-4576-989a-e360a936182b@rowland.harvard.edu> (raw)
In-Reply-To: <00000000000047c61c05fb85d44e@google.com>

On Fri, May 12, 2023 at 02:31:34PM -0700, syzbot wrote:
> 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-13 13:42 UTC|newest]

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

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=bc3011b3-e742-4576-989a-e360a936182b@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --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=syzbot+1cb937c125adb93fad2d@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

all inboxes | Powered by JetHome®