syzbot


inconsistent lock state in sync_timeline_debug_remove

Status: upstream: reported C repro on 2022/02/14 08:30
Subsystems: dri media
[Documentation on labels]
Reported-by: syzbot+7dcd254b8987a29f6450@syzkaller.appspotmail.com
First crash: 893d, last: 48d
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: inconsistent lock state in sync_timeline_debug_remove (log)
Repro: C syz .config
  
Discussions (15)
Title Replies (including bot) Last reply
[syzbot] Monthly media report (Jun 2024) 0 (1) 2024/06/15 17:49
[syzbot] Monthly dri report (Jun 2024) 0 (1) 2024/06/10 12:41
[syzbot] Monthly media report (May 2024) 0 (1) 2024/05/14 20:49
[syzbot] Monthly dri report (May 2024) 0 (1) 2024/05/06 13:18
[syzbot] Monthly media report (Apr 2024) 0 (1) 2024/04/13 14:40
[syzbot] Monthly dri report (Apr 2024) 0 (1) 2024/04/05 12:37
[syzbot] Monthly media report (Mar 2024) 0 (1) 2024/03/13 13:39
[syzbot] Monthly dri report (Mar 2024) 0 (1) 2024/03/05 11:09
[syzbot] Monthly media report (Feb 2024) 0 (1) 2024/02/12 10:24
[syzbot] Monthly dri report (Feb 2024) 0 (1) 2024/02/02 21:05
[syzbot] Monthly media report (Jan 2024) 0 (1) 2024/01/10 20:36
[syzbot] Monthly dri report (Jan 2024) 0 (1) 2024/01/02 13:36
[syzbot] Monthly media report (Dec 2023) 0 (1) 2023/12/11 09:40
[syzbot] Monthly dri report (Nov 2023) 0 (1) 2023/11/30 20:33
[syzbot] inconsistent lock state in sync_timeline_debug_remove 0 (1) 2022/02/14 08:30
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 inconsistent lock state in sync_timeline_debug_remove (2) 3 69d 82d 0/3 upstream: reported on 2024/05/01 22:11
linux-4.14 inconsistent lock state in sync_timeline_debug_remove C 1 519d 881d 0/1 upstream: reported C repro on 2022/02/22 17:04
linux-5.15 inconsistent lock state in sync_timeline_debug_remove origin:upstream missing-backport C error 20 66d 195d 0/3 upstream: reported C repro on 2024/01/09 18:24
linux-4.19 inconsistent lock state in sync_timeline_debug_remove C error 1 886d 886d 0/1 upstream: reported C repro on 2022/02/18 00:33
linux-6.1 inconsistent lock state in sync_timeline_debug_remove 1 254d 254d 0/3 auto-obsoleted due to no activity on 2024/02/19 12:00
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/06/23 03:49 27m retest repro upstream OK log
2024/06/22 13:55 24m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci OK log
2024/06/22 13:55 36m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci OK log
2024/06/20 07:20 21m retest repro upstream OK log
2024/06/20 07:20 21m retest repro upstream OK log
2024/06/20 07:20 21m retest repro upstream OK log
2024/06/20 07:20 23m retest repro upstream OK log
2024/06/20 07:20 21m retest repro upstream OK log
2024/06/19 02:37 16m retest repro upstream error
2024/06/19 02:37 16m retest repro upstream error
Fix bisection attempts (5)
Created Duration User Patch Repo Result
2023/10/29 19:15 1h12m bisect fix upstream OK (0) job log log
2023/05/31 05:21 21m bisect fix upstream OK (0) job log log
2023/03/20 19:48 22m bisect fix upstream OK (0) job log log
2023/02/06 21:03 21m bisect fix upstream OK (0) job log log
2022/04/20 21:51 18m bisect fix upstream OK (0) job log log

Sample crash report:
================================
WARNING: inconsistent lock state
6.6.0-syzkaller-15859-g89cdf9d55601 #0 Not tainted
--------------------------------
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
syz-executor367/5174 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffffffff8ddfbe18 (sync_timeline_list_lock){?.+.}-{2:2}, at: sync_timeline_debug_remove+0x29/0x1a0 drivers/dma-buf/sync_debug.c:31
{HARDIRQ-ON-W} state was registered at:
  __trace_hardirqs_on_caller kernel/locking/lockdep.c:4291 [inline]
  lockdep_hardirqs_on_prepare kernel/locking/lockdep.c:4358 [inline]
  lockdep_hardirqs_on_prepare+0x139/0x410 kernel/locking/lockdep.c:4310
  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:401 [inline]
  sync_print_obj drivers/dma-buf/sync_debug.c:118 [inline]
  sync_info_debugfs_show+0xef/0x200 drivers/dma-buf/sync_debug.c:153
  seq_read_iter+0x4e5/0x1280 fs/seq_file.c:230
  seq_read+0x196/0x240 fs/seq_file.c:162
  vfs_read+0x1ce/0x8f0 fs/read_write.c:468
  ksys_read+0x12f/0x250 fs/read_write.c:613
  do_syscall_x64 arch/x86/entry/common.c:51 [inline]
  do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82
  entry_SYSCALL_64_after_hwframe+0x63/0x6b
irq event stamp: 19360
hardirqs last  enabled at (19359): [<ffffffff8a856893>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last  enabled at (19359): [<ffffffff8a856893>] _raw_spin_unlock_irq+0x23/0x50 kernel/locking/spinlock.c:202
hardirqs last disabled at (19360): [<ffffffff8a81787e>] sysvec_irq_work+0xe/0xc0 arch/x86/kernel/irq_work.c:17
softirqs last  enabled at (18224): [<ffffffff814f0ef7>] invoke_softirq kernel/softirq.c:427 [inline]
softirqs last  enabled at (18224): [<ffffffff814f0ef7>] __irq_exit_rcu kernel/softirq.c:632 [inline]
softirqs last  enabled at (18224): [<ffffffff814f0ef7>] irq_exit_rcu+0xb7/0x120 kernel/softirq.c:644
softirqs last disabled at (18215): [<ffffffff814f0ef7>] invoke_softirq kernel/softirq.c:427 [inline]
softirqs last disabled at (18215): [<ffffffff814f0ef7>] __irq_exit_rcu kernel/softirq.c:632 [inline]
softirqs last disabled at (18215): [<ffffffff814f0ef7>] irq_exit_rcu+0xb7/0x120 kernel/softirq.c:644

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(sync_timeline_list_lock);
  <Interrupt>
    lock(sync_timeline_list_lock);

 *** DEADLOCK ***

no locks held by syz-executor367/5174.

stack backtrace:
CPU: 0 PID: 5174 Comm: syz-executor367 Not tainted 6.6.0-syzkaller-15859-g89cdf9d55601 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 print_usage_bug kernel/locking/lockdep.c:3970 [inline]
 valid_state kernel/locking/lockdep.c:4012 [inline]
 mark_lock_irq kernel/locking/lockdep.c:4215 [inline]
 mark_lock+0x11f3/0x1950 kernel/locking/lockdep.c:4677
 mark_usage kernel/locking/lockdep.c:4563 [inline]
 __lock_acquire+0x163e/0x5de0 kernel/locking/lockdep.c:5090
 lock_acquire kernel/locking/lockdep.c:5753 [inline]
 lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0x3a/0x50 kernel/locking/spinlock.c:162
 sync_timeline_debug_remove+0x29/0x1a0 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+0x262/0x340 drivers/dma-buf/sw_sync.c:144
 dma_fence_release+0x2ef/0x500 drivers/dma-buf/dma-fence.c:560
 kref_put include/linux/kref.h:65 [inline]
 dma_fence_put include/linux/dma-fence.h:296 [inline]
 dma_fence_put include/linux/dma-fence.h:293 [inline]
 dma_fence_array_release+0x1fa/0x2e0 drivers/dma-buf/dma-fence-array.c:120
 dma_fence_release+0x2ef/0x500 drivers/dma-buf/dma-fence.c:560
 kref_put include/linux/kref.h:65 [inline]
 dma_fence_put include/linux/dma-fence.h:296 [inline]
 dma_fence_put include/linux/dma-fence.h:293 [inline]
 irq_dma_fence_array_work+0xa9/0xd0 drivers/dma-buf/dma-fence-array.c:52
 irq_work_single+0x1b5/0x260 kernel/irq_work.c:221
 irq_work_run_list kernel/irq_work.c:252 [inline]
 irq_work_run_list+0x92/0xc0 kernel/irq_work.c:235
 irq_work_run+0x58/0xd0 kernel/irq_work.c:261
 __sysvec_irq_work+0x82/0x390 arch/x86/kernel/irq_work.c:22
 sysvec_irq_work+0x8e/0xc0 arch/x86/kernel/irq_work.c:17
 </IRQ>
 <TASK>
 asm_sysvec_irq_work+0x1a/0x20 arch/x86/include/asm/idtentry.h:670
RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:160 [inline]
RIP: 0010:_raw_spin_unlock_irq+0x29/0x50 kernel/locking/spinlock.c:202
Code: 90 f3 0f 1e fa 53 48 8b 74 24 08 48 89 fb 48 83 c7 18 e8 1a 88 e2 f6 48 89 df e8 12 07 e3 f6 e8 cd ed 08 f7 fb bf 01 00 00 00 <e8> 62 53 d4 f6 65 8b 05 63 54 7e 75 85 c0 74 02 5b c3 e8 50 19 7b
RSP: 0018:ffffc900035bfcc8 EFLAGS: 00000206
RAX: 0000000000004b9f RBX: ffff888020d8be50 RCX: 1ffffffff1e31eb9
RDX: 0000000000000000 RSI: ffffffff8acca9a0 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff8f192857 R11: 0000000000000000 R12: ffff888020d8be00
R13: dffffc0000000000 R14: ffff888020d8be00 R15: ffff888020d8be50
 spin_unlock_irq include/linux/spinlock.h:401 [inline]
 sw_sync_debugfs_release+0x164/0x240 drivers/dma-buf/sw_sync.c:321
 __fput+0x270/0xbb0 fs/file_table.c:394
 task_work_run+0x14d/0x240 kernel/task_work.c:180
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa92/0x2ae0 kernel/exit.c:871
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
 __do_sys_exit_group kernel/exit.c:1032 [inline]
 __se_sys_exit_group kernel/exit.c:1030 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1030
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f4d08a39ef9
Code: Unable to access opcode bytes at 0x7f4d08a39ecf.
RSP: 002b:00007fff18c00958 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4d08a39ef9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f4d08ab42b0 R08: ffffffffffffffb8 R09: 00000000000ac5f8
R10: 00000000000ac5f8 R11: 0000000000000246 R12: 00007f4d08ab42b0
R13: 0000000000000000 R14: 00007f4d08ab4d00 R15: 00007f4d08a0bcf0
 </TASK>
----------------
Code disassembly (best guess):
   0:	90                   	nop
   1:	f3 0f 1e fa          	endbr64
   5:	53                   	push   %rbx
   6:	48 8b 74 24 08       	mov    0x8(%rsp),%rsi
   b:	48 89 fb             	mov    %rdi,%rbx
   e:	48 83 c7 18          	add    $0x18,%rdi
  12:	e8 1a 88 e2 f6       	call   0xf6e28831
  17:	48 89 df             	mov    %rbx,%rdi
  1a:	e8 12 07 e3 f6       	call   0xf6e30731
  1f:	e8 cd ed 08 f7       	call   0xf708edf1
  24:	fb                   	sti
  25:	bf 01 00 00 00       	mov    $0x1,%edi
* 2a:	e8 62 53 d4 f6       	call   0xf6d45391 <-- trapping instruction
  2f:	65 8b 05 63 54 7e 75 	mov    %gs:0x757e5463(%rip),%eax        # 0x757e5499
  36:	85 c0                	test   %eax,%eax
  38:	74 02                	je     0x3c
  3a:	5b                   	pop    %rbx
  3b:	c3                   	ret
  3c:	e8                   	.byte 0xe8
  3d:	50                   	push   %rax
  3e:	19                   	.byte 0x19
  3f:	7b                   	.byte 0x7b

Crashes (335):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/11/10 23:55 upstream 89cdf9d55601 910357f9 .config console log report syz C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2023/11/08 06:18 upstream 13d88ac54ddd 83211397 .config console log report syz C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/01/28 07:26 upstream 8a696a29c690 cc4a4020 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in sync_timeline_debug_remove
2022/08/04 04:05 upstream 200e340f2196 1c9013ac .config strace log report syz C ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2022/07/29 22:59 upstream 6e2c0490769e fef302b1 .config console log report syz C ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2022/07/04 01:58 upstream 69cb6c6556ad 1434eec0 .config strace log report syz C ci-upstream-kasan-gce-smack-root inconsistent lock state in sync_timeline_debug_remove
2022/06/28 15:56 upstream 941e3e791269 ef82eb2c .config strace log report syz C ci-upstream-kasan-gce-smack-root inconsistent lock state in sync_timeline_debug_remove
2022/05/19 16:55 upstream f993aed406ea 50c53f39 .config strace log report syz C ci-upstream-kasan-gce-root inconsistent lock state in sync_timeline_debug_remove
2022/05/15 22:04 upstream bc403203d65a 744a39e2 .config strace log report syz C ci-upstream-kasan-gce-root inconsistent lock state in sync_timeline_debug_remove
2022/02/17 21:02 upstream f71077a4d84b 3cd800e4 .config console log report syz C ci-upstream-kasan-gce inconsistent lock state in sync_timeline_debug_remove
2022/02/10 08:25 upstream f4bc5bbb5fef 0b33604d .config console log report syz C ci-upstream-kasan-gce inconsistent lock state in sync_timeline_debug_remove
2022/06/29 05:22 linux-next cb71b93c2dc3 496a8536 .config strace log report syz C ci-upstream-linux-next-kasan-gce-root inconsistent lock state in sync_timeline_debug_remove
2022/02/17 20:05 linux-next ef6b35306dd8 3cd800e4 .config console log report syz C ci-upstream-linux-next-kasan-gce-root inconsistent lock state in sync_timeline_debug_remove
2024/04/23 13:17 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6a71d2909427 21339d7b .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 inconsistent lock state in sync_timeline_debug_remove
2024/01/28 07:58 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca cc4a4020 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 inconsistent lock state in sync_timeline_debug_remove
2024/05/28 20:56 upstream e0cce98fe279 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/26 21:21 upstream 6fbf71854e2d a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/25 04:23 upstream 0b32d436c015 a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/25 03:14 upstream 0b32d436c015 a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/23 21:00 upstream 8f6a15f095a6 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/23 19:38 upstream 8f6a15f095a6 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/22 16:46 upstream 8f6a15f095a6 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/22 10:20 upstream 8f6a15f095a6 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/21 03:11 upstream 1b0361620970 c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/20 08:46 upstream 61307b7be41a c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/19 20:55 upstream 61307b7be41a c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/19 10:15 upstream 0450d2083be6 c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/19 08:16 upstream 0450d2083be6 c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/18 18:59 upstream 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/18 18:30 upstream 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/17 19:59 upstream ff2632d7d08e a12e99e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/17 14:34 upstream ea5f6ad9ad96 a12e99e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/17 10:20 upstream ea5f6ad9ad96 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/16 08:34 upstream 3c999d1ae3c7 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/15 04:13 upstream 1b10b390d945 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/13 09:33 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/13 07:27 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/12 10:02 upstream cf87f46fd34d 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/10 16:42 upstream 448b3fe5a0ea f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/10 09:06 upstream 448b3fe5a0ea de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/10 04:07 upstream 45db3ab70092 de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/05/09 17:07 upstream 45db3ab70092 de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root inconsistent lock state in sync_timeline_debug_remove
2024/05/05 21:11 upstream b9158815de52 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root inconsistent lock state in sync_timeline_debug_remove
2024/02/01 13:33 upstream 6764c317b6bb 81024119 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/24 05:37 upstream 6d69b6c12fce c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/21 08:58 upstream 8f6a15f095a6 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/17 06:42 upstream ea5f6ad9ad96 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/14 19:10 upstream 6bfd2d442af5 fdb4c10c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/13 15:48 upstream a38297e3fb01 c97f7904 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/12 19:30 upstream ba16c1cf11c9 9026e142 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/10 23:23 upstream f4345f05c0df 9026e142 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/10 22:00 upstream f4345f05c0df 9026e142 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/08 13:33 upstream dccb07f2914c 9473be88 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/06 22:01 upstream ee5b455b0ada fa7a5cf0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream inconsistent lock state in sync_timeline_debug_remove
2024/05/31 22:28 upstream d8ec19857b09 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/27 19:11 upstream 2bfcfd584ff5 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/26 00:09 upstream 54f71b0369c9 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/24 05:12 upstream 6d69b6c12fce c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/23 15:14 upstream c760b3725e52 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/23 00:45 upstream 5f16eb0549ab c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/13 08:30 upstream a38297e3fb01 9026e142 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/12 12:40 upstream cf87f46fd34d 9026e142 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/11 12:17 upstream cf87f46fd34d 9026e142 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/09 13:41 upstream 45db3ab70092 de979bc2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/09 01:21 upstream 6d7ddd805123 20bf80e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/09 00:14 upstream 6d7ddd805123 20bf80e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/08 20:35 upstream 6d7ddd805123 9473be88 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2024/05/06 22:39 upstream ee5b455b0ada fa7a5cf0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 inconsistent lock state in sync_timeline_debug_remove
2023/01/07 00:00 upstream 1f5abbd77e2c 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in sync_timeline_debug_remove
2024/06/05 02:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c e1e2c66e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 inconsistent lock state in sync_timeline_debug_remove
2024/05/09 15:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1c9135d29e9e de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 inconsistent lock state in sync_timeline_debug_remove
2023/06/24 04:07 linux-next 8d2be868b42c 09ffe269 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in sync_timeline_debug_remove
* Struck through repros no longer work on HEAD.