ci starts bisection 2023-03-20 19:48:33.933320748 +0000 UTC m=+257597.212697835 bisecting fixing commit since 200e340f2196d7fd427a5810d06e893b932f145a building syzkaller on 1c9013acc70de325dbb554c8c40c17ed02eff33f ensuring issue is reproducible on original commit 200e340f2196d7fd427a5810d06e893b932f145a testing commit 200e340f2196d7fd427a5810d06e893b932f145a gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: ecc740d73b5c64f6fa325524156fda950ca6b338448d5e8410f74de9006d258c run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: crashed: inconsistent lock state in sync_timeline_debug_remove run #2: crashed: inconsistent lock state in sync_timeline_debug_remove run #3: crashed: inconsistent lock state in sync_timeline_debug_remove run #4: crashed: inconsistent lock state in sync_timeline_debug_remove run #5: crashed: inconsistent lock state in sync_timeline_debug_remove run #6: crashed: inconsistent lock state in sync_timeline_debug_remove run #7: crashed: inconsistent lock state in sync_timeline_debug_remove run #8: crashed: inconsistent lock state in sync_timeline_debug_remove run #9: crashed: inconsistent lock state in sync_timeline_debug_remove run #10: crashed: inconsistent lock state in sync_timeline_debug_remove run #11: crashed: inconsistent lock state in sync_timeline_debug_remove run #12: crashed: inconsistent lock state in sync_timeline_debug_remove run #13: crashed: inconsistent lock state in sync_timeline_debug_remove run #14: crashed: inconsistent lock state in sync_timeline_debug_remove run #15: crashed: inconsistent lock state in sync_timeline_debug_remove run #16: crashed: inconsistent lock state in sync_timeline_debug_remove run #17: crashed: inconsistent lock state in sync_timeline_debug_remove run #18: crashed: inconsistent lock state in sync_timeline_debug_remove run #19: crashed: inconsistent lock state in sync_timeline_debug_remove testing current HEAD 7d31677bb7b1944ac89e9155110dc1b9acbb3895 testing commit 7d31677bb7b1944ac89e9155110dc1b9acbb3895 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 7e534540f6e57931bf75e495f4a0343ae2d62e20690e0dc614383eafaa8a2317 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: crashed: inconsistent lock state in sync_timeline_debug_remove run #2: crashed: inconsistent lock state in sync_timeline_debug_remove run #3: crashed: inconsistent lock state in sync_timeline_debug_remove run #4: crashed: inconsistent lock state in sync_timeline_debug_remove run #5: crashed: inconsistent lock state in sync_timeline_debug_remove run #6: crashed: inconsistent lock state in sync_timeline_debug_remove run #7: crashed: inconsistent lock state in sync_timeline_debug_remove run #8: crashed: inconsistent lock state in sync_timeline_debug_remove run #9: crashed: inconsistent lock state in sync_timeline_debug_remove revisions tested: 2, total time: 21m49.440613598s (build: 14m3.588051307s, test: 6m51.002420261s) the crash still happens on HEAD commit msg: gpu: host1x: fix uninitialized variable use crash: inconsistent lock state in sync_timeline_debug_remove ================================ WARNING: inconsistent lock state 6.3.0-rc3-syzkaller #0 Not tainted -------------------------------- inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage. syz-executor.0/5533 [HC1[1]:SC0[0]:HE0:SE1] takes: ffffffff8bd36438 (sync_timeline_list_lock){?.+.}-{2:2}, at: sync_timeline_debug_remove+0x19/0x180 drivers/dma-buf/sync_debug.c:31 {HARDIRQ-ON-W} state was registered at: __trace_hardirqs_on_caller kernel/locking/lockdep.c:4255 [inline] lockdep_hardirqs_on_prepare kernel/locking/lockdep.c:4322 [inline] lockdep_hardirqs_on_prepare+0x135/0x400 kernel/locking/lockdep.c:4274 trace_hardirqs_on+0x32/0x40 kernel/trace/trace_preemptirq.c:61 __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202 spin_unlock_irq include/linux/spinlock.h:400 [inline] sync_print_obj drivers/dma-buf/sync_debug.c:118 [inline] sync_info_debugfs_show+0xd4/0x1d0 drivers/dma-buf/sync_debug.c:153 seq_read_iter+0x3fa/0x10e0 fs/seq_file.c:230 seq_read+0x161/0x200 fs/seq_file.c:162 vfs_read+0x1b8/0x7c0 fs/read_write.c:468 ksys_read+0xee/0x1c0 fs/read_write.c:613 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd irq event stamp: 3596 hardirqs last enabled at (3595): [] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline] hardirqs last enabled at (3595): [] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202 hardirqs last disabled at (3596): [] sysvec_irq_work+0xb/0xc0 arch/x86/kernel/irq_work.c:17 softirqs last enabled at (506): [] invoke_softirq kernel/softirq.c:445 [inline] softirqs last enabled at (506): [] __irq_exit_rcu+0x114/0x190 kernel/softirq.c:650 softirqs last disabled at (403): [] invoke_softirq kernel/softirq.c:445 [inline] softirqs last disabled at (403): [] __irq_exit_rcu+0x114/0x190 kernel/softirq.c:650 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(sync_timeline_list_lock); lock(sync_timeline_list_lock); *** DEADLOCK *** no locks held by syz-executor.0/5533. stack backtrace: CPU: 1 PID: 5533 Comm: syz-executor.0 Not tainted 6.3.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x60/0xa0 lib/dump_stack.c:106 print_usage_bug kernel/locking/lockdep.c:3934 [inline] valid_state kernel/locking/lockdep.c:3976 [inline] mark_lock_irq kernel/locking/lockdep.c:4179 [inline] mark_lock.part.0+0x1110/0x1970 kernel/locking/lockdep.c:4635 mark_lock kernel/locking/lockdep.c:4599 [inline] mark_usage kernel/locking/lockdep.c:4527 [inline] __lock_acquire+0x1690/0x5d40 kernel/locking/lockdep.c:5010 lock_acquire kernel/locking/lockdep.c:5669 [inline] lock_acquire+0x1ab/0x520 kernel/locking/lockdep.c:5634 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162 sync_timeline_debug_remove+0x19/0x180 drivers/dma-buf/sync_debug.c:31 sync_timeline_free drivers/dma-buf/sw_sync.c:104 [inline] kref_put include/linux/kref.h:65 [inline] sync_timeline_put drivers/dma-buf/sw_sync.c:116 [inline] timeline_fence_release+0x1f6/0x2c0 drivers/dma-buf/sw_sync.c:144 kref_put include/linux/kref.h:65 [inline] dma_fence_put include/linux/dma-fence.h:276 [inline] dma_fence_array_release+0x170/0x240 drivers/dma-buf/dma-fence-array.c:120 irq_work_single+0x106/0x210 kernel/irq_work.c:211 irq_work_run_list kernel/irq_work.c:242 [inline] irq_work_run_list+0x6a/0x90 kernel/irq_work.c:225 irq_work_run+0x4f/0xd0 kernel/irq_work.c:251 __sysvec_irq_work+0x95/0x2d0 arch/x86/kernel/irq_work.c:22 sysvec_irq_work+0x8e/0xc0 arch/x86/kernel/irq_work.c:17 asm_sysvec_irq_work+0x16/0x20 arch/x86/include/asm/idtentry.h:671 RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:160 [inline] RIP: 0010:_raw_spin_unlock_irq+0x25/0x40 kernel/locking/spinlock.c:202 Code: 0f 1f 44 00 00 55 48 8b 74 24 08 48 89 fd 48 83 c7 18 e8 de 8a 89 f8 48 89 ef e8 26 f7 89 f8 e8 71 39 a9 f8 fb bf 01 00 00 00 76 30 7c f8 65 8b 05 d7 c8 34 77 85 c0 74 02 5d c3 e8 c4 8a 31 RSP: 0018:ffffc9000344faa0 EFLAGS: 00000202 RAX: 0000000000000e0b RBX: ffff8880281d3100 RCX: 1ffffffff19e79f9 RDX: 0000000000000000 RSI: ffffffff890bec00 RDI: 0000000000000001 RBP: ffff8880281d3150 R08: 0000000000000001 R09: 0000000000000001 R10: fffffbfff19e8002 R11: 0000000000000000 R12: dffffc0000000000 R13: ffff8880281d3100 R14: ffff8880281d3150 R15: ffff888077848430 spin_unlock_irq include/linux/spinlock.h:400 [inline] sw_sync_debugfs_release+0x134/0x1e0 drivers/dma-buf/sw_sync.c:321 __fput+0x1fa/0x9a0 fs/file_table.c:321 task_work_run+0x12b/0x220 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x924/0x2470 kernel/exit.c:869 do_group_exit+0xb0/0x250 kernel/exit.c:1019 get_signal+0x1d26/0x1f90 kernel/signal.c:2859 arch_do_signal_or_restart+0x75/0x5b0 arch/x86/kernel/signal.c:306 exit_to_user_mode_loop kernel/entry/common.c:168 [inline] exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:296 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f1a68289209 Code: Unable to access opcode bytes at 0x7f1a682891df. RSP: 002b:00007f1a6939f218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: 0000000000000001 RBX: 00007f1a6839bf68 RCX: 00007f1a68289209 RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007f1a6839bf6c RBP: 00007f1a6839bf60 R08: 00007ffc0e4d4080 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 00007f1a6839bf6c R13: 00007ffc0e4958df R14: 00007f1a6939f300 R15: 0000000000022000 ---------------- Code disassembly (best guess): 0: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1) 5: 55 push %rbp 6: 48 8b 74 24 08 mov 0x8(%rsp),%rsi b: 48 89 fd mov %rdi,%rbp e: 48 83 c7 18 add $0x18,%rdi 12: e8 de 8a 89 f8 callq 0xf8898af5 17: 48 89 ef mov %rbp,%rdi 1a: e8 26 f7 89 f8 callq 0xf889f745 1f: e8 71 39 a9 f8 callq 0xf8a93995 24: fb sti 25: bf 01 00 00 00 mov $0x1,%edi * 2a: e8 76 30 7c f8 callq 0xf87c30a5 <-- trapping instruction 2f: 65 8b 05 d7 c8 34 77 mov %gs:0x7734c8d7(%rip),%eax # 0x7734c90d 36: 85 c0 test %eax,%eax 38: 74 02 je 0x3c 3a: 5d pop %rbp 3b: c3 retq 3c: e8 .byte 0xe8 3d: c4 .byte 0xc4 3e: 8a 31 mov (%rcx),%dh