ci starts bisection 2023-05-24 22:34:01.01673403 +0000 UTC m=+35686.940493569 bisecting fixing commit since ef4d3ea40565a781c25847e9cb96c1bd9f462bc6 building syzkaller on e080de16713b9dbf308cdd7bcb85b58293e46e33 ensuring issue is reproducible on original commit ef4d3ea40565a781c25847e9cb96c1bd9f462bc6 testing commit ef4d3ea40565a781c25847e9cb96c1bd9f462bc6 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 7a9759109bbe7765e040d4945f4073f259bcee0da918245991ad825641d5f546 run #0: crashed: inconsistent lock state in sync_info_debugfs_show run #1: crashed: inconsistent lock state in sync_info_debugfs_show run #2: crashed: inconsistent lock state in sync_info_debugfs_show run #3: crashed: inconsistent lock state in sync_info_debugfs_show run #4: crashed: inconsistent lock state in sync_info_debugfs_show run #5: crashed: INFO: rcu detected stall in corrupted run #6: crashed: inconsistent lock state in sync_info_debugfs_show run #7: crashed: INFO: rcu detected stall in corrupted run #8: crashed: inconsistent lock state in sync_info_debugfs_show run #9: crashed: INFO: rcu detected stall in corrupted run #10: crashed: INFO: rcu detected stall in corrupted run #11: crashed: INFO: rcu detected stall in corrupted run #12: crashed: INFO: rcu detected stall in corrupted run #13: crashed: INFO: rcu detected stall in corrupted run #14: crashed: INFO: rcu detected stall in corrupted run #15: crashed: INFO: rcu detected stall in corrupted run #16: crashed: INFO: rcu detected stall in corrupted run #17: crashed: INFO: rcu detected stall in corrupted run #18: crashed: INFO: rcu detected stall in corrupted run #19: crashed: INFO: rcu detected stall in corrupted testing current HEAD 933174ae28ba72ab8de5b35cb7c98fc211235096 testing commit 933174ae28ba72ab8de5b35cb7c98fc211235096 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 651155bd5007bae6dbe8c3c4262e83f223d0b36afb60ef7590fe8ef9492a49a5 all runs: crashed: inconsistent lock state in sync_info_debugfs_show crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 26m48.362572829s (build: 19m5.730018775s, test: 6m20.370432269s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Merge tag 'spi-fix-v6.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi crash: inconsistent lock state in sync_info_debugfs_show ================================ WARNING: inconsistent lock state 6.4.0-rc3-syzkaller #0 Not tainted -------------------------------- inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage. syz-executor.5/5724 [HC0[0]:SC0[0]:HE0:SE1] takes: ffffffff8c4501f8 (sync_timeline_list_lock){?...}-{2:2}, at: spin_lock_irq include/linux/spinlock.h:375 [inline] ffffffff8c4501f8 (sync_timeline_list_lock){?...}-{2:2}, at: sync_info_debugfs_show+0x29/0x1d0 drivers/dma-buf/sync_debug.c:147 {IN-HARDIRQ-W} state was registered at: lock_acquire kernel/locking/lockdep.c:5691 [inline] lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5656 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x3d/0x60 kernel/locking/spinlock.c:162 sync_timeline_debug_remove+0x1d/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+0x1fa/0x2c0 drivers/dma-buf/sw_sync.c:144 kref_put include/linux/kref.h:65 [inline] dma_fence_put include/linux/dma-fence.h:296 [inline] dma_fence_array_release+0x174/0x250 drivers/dma-buf/dma-fence-array.c:120 irq_work_single+0x10a/0x210 kernel/irq_work.c:221 irq_work_run_list kernel/irq_work.c:252 [inline] irq_work_run_list+0x6a/0x90 kernel/irq_work.c:235 irq_work_run+0x53/0xd0 kernel/irq_work.c:261 __sysvec_irq_work+0x99/0x2d0 arch/x86/kernel/irq_work.c:22 sysvec_irq_work+0x92/0xc0 arch/x86/kernel/irq_work.c:17 asm_sysvec_irq_work+0x1a/0x20 arch/x86/include/asm/idtentry.h:671 __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:160 [inline] _raw_spin_unlock_irq+0x29/0x50 kernel/locking/spinlock.c:202 spin_unlock_irq include/linux/spinlock.h:400 [inline] sw_sync_debugfs_release+0x138/0x1e0 drivers/dma-buf/sw_sync.c:321 __fput+0x1fa/0x9a0 fs/file_table.c:321 task_work_run+0x12f/0x220 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x210/0x240 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline] syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297 do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd irq event stamp: 80 hardirqs last enabled at (79): [] mod_objcg_state+0x595/0xa50 mm/memcontrol.c:3256 hardirqs last disabled at (80): [] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline] hardirqs last disabled at (80): [] _raw_spin_lock_irq+0x45/0x50 kernel/locking/spinlock.c:170 softirqs last enabled at (0): [] copy_process+0x1e9d/0x6c40 kernel/fork.c:2452 softirqs last disabled at (0): [<0000000000000000>] 0x0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(sync_timeline_list_lock); lock(sync_timeline_list_lock); *** DEADLOCK *** 3 locks held by syz-executor.5/5724: #0: ffff888027b08368 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x9a/0xb0 fs/file.c:1047 #1: ffff8880239fd668 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xc2/0x10f0 fs/seq_file.c:182 #2: ffffffff8c4501f8 (sync_timeline_list_lock){?...}-{2:2}, at: spin_lock_irq include/linux/spinlock.h:375 [inline] #2: ffffffff8c4501f8 (sync_timeline_list_lock){?...}-{2:2}, at: sync_info_debugfs_show+0x29/0x1d0 drivers/dma-buf/sync_debug.c:147 stack backtrace: CPU: 0 PID: 5724 Comm: syz-executor.5 Not tainted 6.4.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/16/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x64/0xb0 lib/dump_stack.c:106 print_usage_bug kernel/locking/lockdep.c:3944 [inline] valid_state kernel/locking/lockdep.c:3986 [inline] mark_lock_irq kernel/locking/lockdep.c:4189 [inline] mark_lock.part.0+0x1110/0x1970 kernel/locking/lockdep.c:4651 mark_lock kernel/locking/lockdep.c:4615 [inline] mark_held_locks+0x9f/0xe0 kernel/locking/lockdep.c:4247 __trace_hardirqs_on_caller kernel/locking/lockdep.c:4265 [inline] lockdep_hardirqs_on_prepare kernel/locking/lockdep.c:4332 [inline] lockdep_hardirqs_on_prepare+0x139/0x410 kernel/locking/lockdep.c:4284 trace_hardirqs_on+0x36/0x40 kernel/trace/trace_preemptirq.c:61 __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline] _raw_spin_unlock_irq+0x23/0x50 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+0xd8/0x1d0 drivers/dma-buf/sync_debug.c:153 seq_read_iter+0x3fe/0x10f0 fs/seq_file.c:230 seq_read+0x165/0x200 fs/seq_file.c:162 vfs_read+0x16f/0x7b0 fs/read_write.c:468 ksys_read+0xf2/0x1c0 fs/read_write.c:613 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f4aa848c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f4aa9227168 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00007f4aa85abf80 RCX: 00007f4aa848c0d9 RDX: 0000000000002020 RSI: 0000000020002200 RDI: 0000000000000003 RBP: 00007f4aa84e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff4051ecdf R14: 00007f4aa9227300 R15: 0000000000022000