Messages in this thread | | | From | Andrey Konovalov <> | Date | Thu, 12 Dec 2019 17:08:01 +0100 | Subject | Re: KASAN: use-after-free Read in usbvision_v4l2_open |
| |
On Wed, Dec 11, 2019 at 5:22 PM Alan Stern <stern@rowland.harvard.edu> wrote: > > On Wed, 11 Dec 2019, Dmitry Vyukov wrote: > > > > > By the way, do you know why syzbot sent _two_ reply messages? One with > > > > message ID <00000000000031a0af05995eca0b@google.com> and the other with > > > > message ID <000000000000441a4205995eca11@google.com>? It seems like > > > > overkill. > > > > > > Hm, I'm not sure. Dmitry? > > > > I would assume it received 2 emails (second from syzkaller-bugs@ > > mailing list) and deduplication logic did not work somehow. So it > > replied to both. > > Does that mean when I send in a test request, it's better to omit > syzkaller-bugs from the CC: list? > > Also, whatever did happen to the most recent test request (the one sent > to syzbot+7fa38a608b1075dfd634 even though it was meant to test the > bug reported by syzbot+c7b0ec009a216143df30)? Did it truly fail to > build? I can't find anything about it in the dashboard link for either > bug report, and I haven't gotten a reply from syzbot.
Yes, the patch failed due to msleep() being undefined in that source file. I'm not sure why syzbot didn't send a response. Could you try resending the patch as the reply to that other syzbot report?
| |