Hello, syzbot found the following issue on: HEAD commit: 83bdc727 random32: remove net_rand_state from the latent e.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=176e5d12900000 kernel config: https://syzkaller.appspot.com/x/.config?x=e59ee776d5aa8d55 dashboard link: https://syzkaller.appspot.com/bug?extid=f4fb0eaafdb51c32a153 compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d5ed24900000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1381a56c900000 The issue was bisected to: commit a4585c31c5018578b4abf699ddfdff719dd1c313 Author: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx> Date: Tue Oct 18 19:44:09 2016 +0000 [media] marvell-ccic: don't break long lines bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=160d627c900000 final oops: https://syzkaller.appspot.com/x/report.txt?x=150d627c900000 console output: https://syzkaller.appspot.com/x/log.txt?x=110d627c900000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+f4fb0eaafdb51c32a153@xxxxxxxxxxxxxxxxxxxxxxxxx Fixes: a4585c31c501 ("[media] marvell-ccic: don't break long lines") ================================================================== BUG: KASAN: null-ptr-deref in instrument_atomic_write include/linux/instrumented.h:71 [inline] BUG: KASAN: null-ptr-deref in set_bit include/asm-generic/bitops/instrumented-atomic.h:28 [inline] BUG: KASAN: null-ptr-deref in amp_read_loc_assoc_final_data+0x115/0x260 net/bluetooth/amp.c:304 Write of size 8 at addr 0000000000000030 by task kworker/u5:2/6842 CPU: 1 PID: 6842 Comm: kworker/u5:2 Not tainted 5.8.0-rc7-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: hci0 hci_rx_work Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1f0/0x31e lib/dump_stack.c:118 __kasan_report mm/kasan/report.c:517 [inline] kasan_report+0x151/0x1d0 mm/kasan/report.c:530 check_memory_region_inline mm/kasan/generic.c:183 [inline] check_memory_region+0x2b5/0x2f0 mm/kasan/generic.c:192 instrument_atomic_write include/linux/instrumented.h:71 [inline] set_bit include/asm-generic/bitops/instrumented-atomic.h:28 [inline] amp_read_loc_assoc_final_data+0x115/0x260 net/bluetooth/amp.c:304 hci_chan_selected_evt net/bluetooth/hci_event.c:4897 [inline] hci_event_packet+0x8289/0x18240 net/bluetooth/hci_event.c:6164 hci_rx_work+0x236/0x9c0 net/bluetooth/hci_core.c:4705 process_one_work+0x789/0xfc0 kernel/workqueue.c:2269 worker_thread+0xaa4/0x1460 kernel/workqueue.c:2415 kthread+0x37e/0x3a0 drivers/block/aoe/aoecmd.c:1234 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 ================================================================== Kernel panic - not syncing: panic_on_warn set ... CPU: 1 PID: 6842 Comm: kworker/u5:2 Tainted: G B 5.8.0-rc7-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: hci0 hci_rx_work Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1f0/0x31e lib/dump_stack.c:118 panic+0x264/0x7a0 kernel/panic.c:231 end_report mm/kasan/report.c:104 [inline] __kasan_report mm/kasan/report.c:520 [inline] kasan_report+0x1c9/0x1d0 mm/kasan/report.c:530 check_memory_region_inline mm/kasan/generic.c:183 [inline] check_memory_region+0x2b5/0x2f0 mm/kasan/generic.c:192 instrument_atomic_write include/linux/instrumented.h:71 [inline] set_bit include/asm-generic/bitops/instrumented-atomic.h:28 [inline] amp_read_loc_assoc_final_data+0x115/0x260 net/bluetooth/amp.c:304 hci_chan_selected_evt net/bluetooth/hci_event.c:4897 [inline] hci_event_packet+0x8289/0x18240 net/bluetooth/hci_event.c:6164 hci_rx_work+0x236/0x9c0 net/bluetooth/hci_core.c:4705 process_one_work+0x789/0xfc0 kernel/workqueue.c:2269 worker_thread+0xaa4/0x1460 kernel/workqueue.c:2415 kthread+0x37e/0x3a0 drivers/block/aoe/aoecmd.c:1234 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 Kernel Offset: disabled Rebooting in 86400 seconds.. --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
