Hello, syzbot found the following issue on: HEAD commit: aef25be35d23 hexagon: Disable constant extender optimizati.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=17d80cf8580000 kernel config: https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f dashboard link: https://syzkaller.appspot.com/bug?extid=fa8378fe580fb09ae553 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/450e0387636e/disk-aef25be3.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/8912f33f56fc/vmlinux-aef25be3.xz kernel image: https://storage.googleapis.com/syzbot-assets/293fd2e7560b/bzImage-aef25be3.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+fa8378fe580fb09ae553@xxxxxxxxxxxxxxxxxxxxxxxxx Oops: general protection fault, probably for non-canonical address 0xdffffc0000000007: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f] CPU: 1 UID: 0 PID: 5826 Comm: kworker/u9:2 Not tainted 6.13.0-rc3-syzkaller-00044-gaef25be35d23 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024 Workqueue: hci6 hci_conn_timeout RIP: 0010:hci_abort_conn+0x147/0x330 net/bluetooth/hci_conn.c:3048 Code: ae 08 0d 00 00 48 89 e8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 ef e8 38 08 4d f7 48 8b 6d 00 48 83 c5 3b 48 89 e8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 22 01 00 00 0f b6 6d 00 48 89 ef 48 c7 RSP: 0018:ffffc9000307fb78 EFLAGS: 00010212 RAX: 0000000000000007 RBX: 0000000000000001 RCX: ffff888059fd5a00 RDX: ffff888059fd5a00 RSI: 0000000000000001 RDI: 0000000000000001 RBP: 000000000000003b R08: ffffffff8ab8d446 R09: ffffffff8aba1f98 R10: 0000000000000002 R11: ffff888059fd5a00 R12: ffff8880669b4000 R13: dffffc0000000000 R14: ffff88802f4fc000 R15: 0000000000000013 FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556cac811000 CR3: 0000000060eee000 CR4: 0000000000350ef0 Call Trace: <TASK> process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa68/0x1840 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f2/0x390 kernel/kthread.c:389 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:hci_abort_conn+0x147/0x330 net/bluetooth/hci_conn.c:3048 Code: ae 08 0d 00 00 48 89 e8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 ef e8 38 08 4d f7 48 8b 6d 00 48 83 c5 3b 48 89 e8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 22 01 00 00 0f b6 6d 00 48 89 ef 48 c7 RSP: 0018:ffffc9000307fb78 EFLAGS: 00010212 RAX: 0000000000000007 RBX: 0000000000000001 RCX: ffff888059fd5a00 RDX: ffff888059fd5a00 RSI: 0000000000000001 RDI: 0000000000000001 RBP: 000000000000003b R08: ffffffff8ab8d446 R09: ffffffff8aba1f98 R10: 0000000000000002 R11: ffff888059fd5a00 R12: ffff8880669b4000 R13: dffffc0000000000 R14: ffff88802f4fc000 R15: 0000000000000013 FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2c1521 CR3: 000000005bf38000 CR4: 0000000000350ef0 ---------------- Code disassembly (best guess): 0: ae scas %es:(%rdi),%al 1: 08 0d 00 00 48 89 or %cl,-0x76b80000(%rip) # 0x89480007 7: e8 48 c1 e8 03 call 0x3e8c154 c: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) 11: 74 08 je 0x1b 13: 48 89 ef mov %rbp,%rdi 16: e8 38 08 4d f7 call 0xf74d0853 1b: 48 8b 6d 00 mov 0x0(%rbp),%rbp 1f: 48 83 c5 3b add $0x3b,%rbp 23: 48 89 e8 mov %rbp,%rax 26: 48 c1 e8 03 shr $0x3,%rax * 2a: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax <-- trapping instruction 2f: 84 c0 test %al,%al 31: 0f 85 22 01 00 00 jne 0x159 37: 0f b6 6d 00 movzbl 0x0(%rbp),%ebp 3b: 48 89 ef mov %rbp,%rdi 3e: 48 rex.W 3f: c7 .byte 0xc7 --- 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. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
