From: syzbot <syzbot+40ac6e73326e79ee8ecb@syzkaller.appspotmail.com>
To: duoming@zju.edu.cn, hverkuil-cisco@xs4all.nl,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] WARNING in smsusb_term_device
Date: Sun, 26 Feb 2023 18:07:20 -0800 [thread overview]
Message-ID: <00000000000063a01505f5a4f0a6@google.com> (raw)
In-Reply-To: <0000000000001c7bf005f549b59d@google.com>
syzbot has bisected this issue to:
commit ebad8e731c1c06adf04621d6fd327b860c0861b5
Author: Duoming Zhou <duoming@zju.edu.cn>
Date: Mon Jan 23 02:04:38 2023 +0000
media: usb: siano: Fix use after free bugs caused by do_submit_urb
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1687af1cc80000
start commit: 8232539f864c Add linux-next specific files for 20230225
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1587af1cc80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1187af1cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4fe68735401a6111
dashboard link: https://syzkaller.appspot.com/bug?extid=40ac6e73326e79ee8ecb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ba7cb0c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16734964c80000
Reported-by: syzbot+40ac6e73326e79ee8ecb@syzkaller.appspotmail.com
Fixes: ebad8e731c1c ("media: usb: siano: Fix use after free bugs caused by do_submit_urb")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-02-27 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 13:16 [syzbot] [media?] WARNING in smsusb_term_device syzbot
2023-02-26 18:41 ` syzbot
2023-02-27 2:07 ` syzbot [this message]
2023-03-01 11:29 ` duoming
[not found] <20230227024127.3574-1-hdanton@sina.com>
2023-02-27 3:15 ` 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=00000000000063a01505f5a4f0a6@google.com \
--to=syzbot+40ac6e73326e79ee8ecb@syzkaller.appspotmail.com \
--cc=duoming@zju.edu.cn \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.