From: syzbot <syzbot+18996170f8096c6174d0@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, khazhy@google.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KASAN: slab-out-of-bounds Read in read_descriptors (3)
Date: Tue, 25 Jul 2023 13:54:30 -0700 [thread overview]
Message-ID: <00000000000000276a060155f0a5@google.com> (raw)
In-Reply-To: <c9bb72e0-8e02-4568-bd43-6897f9c94d12@rowland.harvard.edu>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+18996170f8096c6174d0@syzkaller.appspotmail.com
Tested on:
commit: 6eaae198 Linux 6.5-rc3
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ v6.5-rc3
console output: https://syzkaller.appspot.com/x/log.txt?x=13d77b76a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c7b1aac4a6659b6d
dashboard link: https://syzkaller.appspot.com/bug?extid=18996170f8096c6174d0
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=1339684aa80000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2023-07-25 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 2:55 [syzbot] [usb?] KASAN: slab-out-of-bounds Read in read_descriptors (3) syzbot
2023-07-21 18:10 ` Khazhy Kumykov
2023-07-21 18:23 ` Khazhy Kumykov
2023-07-21 18:56 ` Alan Stern
2023-07-21 22:40 ` Khazhy Kumykov
2023-07-23 2:01 ` Alan Stern
2023-07-23 2:21 ` syzbot
2023-07-25 19:26 ` Alan Stern
2023-07-25 20:42 ` Khazhy Kumykov
2023-07-25 21:30 ` Alan Stern
2023-07-25 21:46 ` Khazhy Kumykov
2023-07-26 4:00 ` Greg KH
2023-08-02 20:00 ` Alan Stern
2023-08-03 6:34 ` Greg KH
2023-07-25 20: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=00000000000000276a060155f0a5@google.com \
--to=syzbot+18996170f8096c6174d0@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=khazhy@google.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 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.