From: syzbot <syzbot+621409285c4156a009b3@syzkaller.appspotmail.com>
To: isely@pobox.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
mchehab@kernel.org, pvrusb2@isely.net, ricardo@marliere.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify
Date: Thu, 12 Oct 2023 15:54:26 -0700 [thread overview]
Message-ID: <0000000000005e814006078cd293@google.com> (raw)
In-Reply-To: <cwc32sg4vzz6akduyvze6tu2dkzpljtvpycuhz43t7lmbzbyvb@jgywtsrcvuzw>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+621409285c4156a009b3@syzkaller.appspotmail.com
Tested on:
commit: ce9ecca0 Linux 6.6-rc2
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
console output: https://syzkaller.appspot.com/x/log.txt?x=10be5209680000
kernel config: https://syzkaller.appspot.com/x/.config?x=59eae8406319284a
dashboard link: https://syzkaller.appspot.com/bug?extid=621409285c4156a009b3
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=131dd84d680000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2023-10-12 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 12:30 [syzbot] [pvrusb2?] [usb?] KASAN: slab-use-after-free Read in pvr2_context_set_notify syzbot
2023-09-27 14:37 ` Ricardo B. Marliere
2023-09-27 14:55 ` [syzbot] [pvrusb2?] " syzbot
2023-10-06 12:17 ` [syzbot] [pvrusb2?] [usb?] " Ricardo B. Marliere
2023-10-06 12:42 ` [syzbot] [pvrusb2?] " syzbot
2023-10-12 22:07 ` [syzbot] [pvrusb2?] [usb?] " Ricardo B. Marliere
2023-10-12 22:54 ` syzbot [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=0000000000005e814006078cd293@google.com \
--to=syzbot+621409285c4156a009b3@syzkaller.appspotmail.com \
--cc=isely@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pvrusb2@isely.net \
--cc=ricardo@marliere.net \
--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).