On Fri, Aug 9, 2019 at 10:52 PM Alan Stern wrote:
>
> On Fri, 9 Aug 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot has tested the proposed patch and the reproducer did not trigger
> > crash:
> >
> > Reported-and-tested-by:
> > syzbot+22ae4e3b9fcc8a5c1...@syzkaller.appspotmail.com
> >
> > Tested o
On Fri, 9 Aug 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+22ae4e3b9fcc8a5c1...@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: e96407b4 usb-fuzzer: main usb gadget fuzzer
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+22ae4e3b9fcc8a5c1...@syzkaller.appspotmail.com
Tested on:
commit: e96407b4 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasa
On Fri, 9 Aug 2019, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=1799392c60
>
On Fri, 9 Aug 2019, Prashant Malani wrote:
> Hi,
>
> I'm trying to get up to speed on USB kernel code. Sounds like
> dev->intf should have been set to NULL for the error path in
> ld_usb_probe() ?
Why should it?
After all, dev gets deallocated at the end of ld_usb_probe(), where
ld_usb_delete(
(Sorry for the resend, I was in HTML mode earlier :S)
Hi,
I'm trying to get up to speed on USB kernel code. Sounds like
dev->intf should have been set to NULL for the error path in
ld_usb_probe() ?
https://elixir.bootlin.com/linux/latest/source/drivers/usb/misc/ldusb.c#L666
On Fri, Aug 9, 2019
Hello,
syzbot found the following crash on:
HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=1799392c60
kernel config: https://syzkaller.appspot.com/x/.