On Wed, Sep 18, 2019 at 8:57 PM Alan Stern wrote:
>
> On Tue, 17 Sep 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot has tested the proposed patch but the reproducer still triggered
> > crash:
> > WARNING in sysfs_remove_group
> >
> > [ cut here ]
> > sysfs group 'power' no
On Tue, 17 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> WARNING in sysfs_remove_group
>
> [ cut here ]
> sysfs group 'power' not found for kobject 'radio0'
Andrey:
Is there any way to tell syzb
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
WARNING in sysfs_remove_group
[ cut here ]
sysfs group 'power' not found for kobject 'radio0'
WARNING: CPU: 0 PID: 2871 at fs/sysfs/group.c:278 sysfs_remove_group
fs/sysfs/group.c:2
On Tue, 17 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot tried to test the proposed patch but build/boot failed:
Oops. Typo.
#syz test: https://github.com/google/kasan.git f0df5c1b
drivers/media/usb/usbvision/usbvision-video.c | 27 ++
1 file changed, 23 insertions(+)
Hello,
syzbot tried to test the proposed patch but build/boot failed:
drivers/usb/typec/altmodes/built-in.a
CC drivers/usb/misc/legousbtower.o
AR drivers/usb/musb/built-in.a
CC drivers/usb/host/sl811-hcd.o
CC drivers/usb/usbip/vhci_sysfs.o
AR drivers/usb/typec
On Tue, 17 Sep 2019, Alan Stern wrote:
> On Tue, 17 Sep 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot has tested the proposed patch but the reproducer still triggered
> > crash:
> > WARNING in sysfs_remove_group
> >
> > [ cut here ]
> > sysfs group 'power' not found
On Tue, 17 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> WARNING in sysfs_remove_group
>
> [ cut here ]
> sysfs group 'power' not found for kobject 'radio3'
> WARNING: CPU: 1 PID: 2883 at fs/sysfs
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
WARNING in sysfs_remove_group
[ cut here ]
sysfs group 'power' not found for kobject 'radio3'
WARNING: CPU: 1 PID: 2883 at fs/sysfs/group.c:278 sysfs_remove_group
fs/sysfs/group.c:2
On Tue, 17 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> possible deadlock in vidioc_querycap
>
>
> WARNING: possible recursive locking detected
> 5.3.0-rc7+ #0 Not tainted
>
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
possible deadlock in vidioc_querycap
WARNING: possible recursive locking detected
5.3.0-rc7+ #0 Not tainted
v4l_id/30
On Mon, 16 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> general protection fault in vidioc_querycap
Same problem in a different part of the code.
Alan Stern
#syz test: https://github.com/google/kasan.git f0df5c1b
dr
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
general protection fault in vidioc_querycap
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN
CPU: 0 PID: 293
On Mon, 16 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f0df5c1b 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=158b66f160
13 matches
Mail list logo