syzbot


inconsistent lock state in valid_state (4)

Status: upstream: reported C repro on 2024/08/19 05:03
Subsystems: linux1394 ppp
[Documentation on labels]
Reported-by: syzbot+d43eb079c2addf2439c3@syzkaller.appspotmail.com
First crash: 225d, last: 45d
Cause bisection: failed (error log, bisect log)
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly ppp report (Dec 2024) 0 (1) 2024/12/27 23:24
[syzbot] Monthly ppp report (Sep 2024) 0 (1) 2024/09/23 09:02
[syzbot] [netfilter?] inconsistent lock state in valid_state (4) 3 (5) 2024/08/22 13:01
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 inconsistent lock state in valid_state (2) missing-backport C done 208 161d 379d 0/3 auto-obsoleted due to no activity on 2024/12/26 10:49
upstream inconsistent lock state in valid_state kernel 1 764d 760d 0/28 auto-obsoleted due to no activity on 2023/06/23 05:39
linux-5.15 inconsistent lock state in valid_state 2 652d 731d 0/3 auto-obsoleted due to no activity on 2023/09/22 20:18
linux-6.1 inconsistent lock state in valid_state (2) origin:upstream missing-backport C done 334 161d 552d 0/3 upstream: reported C repro on 2023/09/22 23:56
upstream inconsistent lock state in valid_state (2) sound C inconclusive 57405 290d 415d 25/28 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm C error 376 237d 286d 27/28 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 1 733d 733d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/01/10 14:30 24m retest repro net-next OK log
2024/10/17 21:56 21m retest repro upstream OK log

Sample crash report:
================================
WARNING: inconsistent lock state
6.14.0-rc2-syzkaller #0 Not tainted
--------------------------------
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
migration/1/23 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffff8880b873e958 ((wq_completion)loop3){?.+.}-{0:0}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598
{HARDIRQ-ON-W} state was registered at:
  lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
  process_one_work kernel/workqueue.c:3211 [inline]
  process_scheduled_works+0x950/0x1840 kernel/workqueue.c:3317
  worker_thread+0x870/0xd30 kernel/workqueue.c:3398
  kthread+0x7ab/0x920 kernel/kthread.c:464
  ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
irq event stamp: 1136
hardirqs last  enabled at (1135): [<ffffffff818e9ef5>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1533 [inline]
hardirqs last  enabled at (1135): [<ffffffff818e9ef5>] finish_lock_switch kernel/sched/core.c:5131 [inline]
hardirqs last  enabled at (1135): [<ffffffff818e9ef5>] finish_task_switch+0x1e5/0x870 kernel/sched/core.c:5249
hardirqs last disabled at (1136): [<ffffffff8bf5c41e>] sysvec_call_function_single+0xe/0xc0 arch/x86/kernel/smp.c:266
softirqs last  enabled at (0): [<ffffffff817f242a>] rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
softirqs last  enabled at (0): [<ffffffff817f242a>] rcu_read_lock include/linux/rcupdate.h:849 [inline]
softirqs last  enabled at (0): [<ffffffff817f242a>] copy_process+0x9fa/0x3d50 kernel/fork.c:2272
softirqs last disabled at (0): [<0000000000000000>] 0x0

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

       CPU0
       ----
  lock((wq_completion)loop3);
  <Interrupt>
    lock((wq_completion)loop3);

 *** DEADLOCK ***

1 lock held by migration/1/23:
 #0: ffff8880b863e958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598

stack backtrace:
CPU: 1 UID: 0 PID: 23 Comm: migration/1 Not tainted 6.14.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Stopper: 0x0 <- 0x0
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_usage_bug+0x62e/0x8b0 kernel/locking/lockdep.c:4040
 valid_state+0x13a/0x1c0 kernel/locking/lockdep.c:4054
 mark_lock_irq+0xbb/0xc20 kernel/locking/lockdep.c:4265
 mark_lock+0x223/0x360 kernel/locking/lockdep.c:4751
 mark_usage kernel/locking/lockdep.c:4637 [inline]
 __lock_acquire+0xbc3/0x2100 kernel/locking/lockdep.c:5182
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
 _raw_spin_lock_nested+0x31/0x40 kernel/locking/spinlock.c:378
 raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598
 _double_lock_balance kernel/sched/sched.h:3006 [inline]
 double_lock_balance kernel/sched/sched.h:3051 [inline]
 find_lock_lowest_rq+0x1e1/0x670 kernel/sched/rt.c:1914
 push_rt_task+0x144/0x790 kernel/sched/rt.c:2048
 rto_push_irq_work_func+0x93/0x350 kernel/sched/rt.c:2249
 irq_work_single+0x136/0x240 kernel/irq_work.c:221
 __flush_smp_call_function_queue+0x9e4/0x1620 kernel/smp.c:574
 __sysvec_call_function_single+0xb8/0x430 arch/x86/kernel/smp.c:271
 instr_sysvec_call_function_single arch/x86/kernel/smp.c:266 [inline]
 sysvec_call_function_single+0x9e/0xc0 arch/x86/kernel/smp.c:266
 </IRQ>
 <TASK>
 asm_sysvec_call_function_single+0x1a/0x20 arch/x86/include/asm/idtentry.h:709
RIP: 0010:finish_task_switch+0x1ea/0x870 kernel/sched/core.c:5251
Code: c9 50 e8 49 0a 0c 00 48 83 c4 08 4c 89 f7 e8 fd 39 00 00 0f 1f 44 00 00 4c 89 f7 e8 80 fd 69 0a e8 7b 75 38 00 fb 48 8b 5d c0 <48> 8d bb 08 16 00 00 48 89 f8 48 c1 e8 03 49 be 00 00 00 00 00 fc
RSP: 0018:ffffc900001d7b08 EFLAGS: 00000286
RAX: 759e5ab9424d5800 RBX: ffff88801d685a00 RCX: ffffffff9a400903
RDX: dffffc0000000000 RSI: ffffffff8c0aa660 RDI: ffffffff8c608ac0
RBP: ffffc900001d7b50 R08: ffffffff901b5c77 R09: 1ffffffff2036b8e
R10: dffffc0000000000 R11: fffffbfff2036b8f R12: 1ffff110170e7eee
R13: dffffc0000000000 R14: ffff8880b873e940 R15: ffff8880b873f770
 context_switch kernel/sched/core.c:5380 [inline]
 __schedule+0x1916/0x4c90 kernel/sched/core.c:6764
 __schedule_loop kernel/sched/core.c:6841 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6856
 smpboot_thread_fn+0x61e/0xa30 kernel/smpboot.c:160
 kthread+0x7ab/0x920 kernel/kthread.c:464
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
----------------
Code disassembly (best guess):
   0:	c9                   	leave
   1:	50                   	push   %rax
   2:	e8 49 0a 0c 00       	call   0xc0a50
   7:	48 83 c4 08          	add    $0x8,%rsp
   b:	4c 89 f7             	mov    %r14,%rdi
   e:	e8 fd 39 00 00       	call   0x3a10
  13:	0f 1f 44 00 00       	nopl   0x0(%rax,%rax,1)
  18:	4c 89 f7             	mov    %r14,%rdi
  1b:	e8 80 fd 69 0a       	call   0xa69fda0
  20:	e8 7b 75 38 00       	call   0x3875a0
  25:	fb                   	sti
  26:	48 8b 5d c0          	mov    -0x40(%rbp),%rbx
* 2a:	48 8d bb 08 16 00 00 	lea    0x1608(%rbx),%rdi <-- trapping instruction
  31:	48 89 f8             	mov    %rdi,%rax
  34:	48 c1 e8 03          	shr    $0x3,%rax
  38:	49                   	rex.WB
  39:	be 00 00 00 00       	mov    $0x0,%esi
  3e:	00 fc                	add    %bh,%ah

Crashes (72):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/10 16:30 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/11/06 20:16 upstream 2e1b3cc9d7f7 3a465482 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/11/05 00:19 upstream 557329bcecc2 509da429 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/10/03 21:56 upstream 7ec462100ef9 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/10/02 15:07 upstream e32cde8d2bd7 a4c7fd36 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/10/02 05:43 upstream e32cde8d2bd7 ea2b66a6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/10/01 16:16 upstream e32cde8d2bd7 ea2b66a6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/10/01 05:17 upstream e32cde8d2bd7 bbd4e0a4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/10/01 00:22 upstream e32cde8d2bd7 bbd4e0a4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in valid_state
2024/09/30 10:51 upstream 9852d85ec9d4 ba29ff75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/29 01:56 upstream 3efc57369a0c ba29ff75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/28 06:01 upstream ad46e8f95e93 440b26ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/27 19:13 upstream e477dba5442c 2b1784d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/27 16:34 upstream 075dbe9f6e3c 2b1784d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/26 15:10 upstream aa486552a110 0d19f247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/25 22:58 upstream aa486552a110 349a68c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/25 09:15 upstream 684a64bf32b6 349a68c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/25 09:14 upstream 684a64bf32b6 349a68c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/25 00:11 upstream 97d8894b6f4c 5643e0e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/24 04:11 upstream abf2050f51fd 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/23 13:14 upstream de5cb0dcb74c 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/23 09:44 upstream de5cb0dcb74c 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/23 09:44 upstream de5cb0dcb74c 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/22 21:04 upstream af9c191ac2a0 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/22 21:04 upstream af9c191ac2a0 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/21 08:42 upstream 1868f9d0260e 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/21 08:41 upstream 1868f9d0260e 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/09/20 09:25 upstream 2004cef11ea0 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/09/14 04:09 upstream e936e7d4a83b 158f4851 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/08/23 13:22 upstream 3d5f968a177d d7d32352 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/08/15 04:57 upstream 9d5906799f7d e4bacdaf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/10/03 05:56 upstream f23aa4c0761a a4c7fd36 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/09/29 16:21 upstream 3efc57369a0c ba29ff75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/09/29 15:18 upstream 3efc57369a0c ba29ff75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/09/25 13:09 upstream 684a64bf32b6 349a68c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/09/23 18:29 upstream de5cb0dcb74c 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/09/23 02:02 upstream af9c191ac2a0 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/09/30 00:45 upstream e7ed34365879 ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/29 05:42 upstream 3efc57369a0c ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/26 02:40 upstream 11a299a7933e 0d19f247 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/14 16:23 upstream b7718454f937 08d8a733 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/14 16:23 upstream b7718454f937 08d8a733 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/12 09:14 upstream 7c6a3a65ace7 d94c83d8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/11 05:15 upstream 8d8d276ba2fb 8ab55d0e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/11 05:15 upstream 8d8d276ba2fb 8ab55d0e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/10 23:57 upstream 8d8d276ba2fb e1ac59f4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/10 23:57 upstream 8d8d276ba2fb e1ac59f4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/08 16:47 upstream d1f2d51b711a 9750182a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/08 16:47 upstream d1f2d51b711a 9750182a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/04 03:18 upstream 88fac17500f4 9d47f20a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/02 18:43 upstream 67784a74e258 1eda0d14 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/02 18:43 upstream 67784a74e258 1eda0d14 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/02 13:14 upstream 67784a74e258 1eda0d14 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/09/02 13:14 upstream 67784a74e258 1eda0d14 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/08/29 01:49 upstream a18093afa393 ef3de9e8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/08/21 23:00 upstream b311c1b497e5 d504e3fd .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/08/21 21:33 upstream b311c1b497e5 d504e3fd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/08/21 21:33 upstream b311c1b497e5 d504e3fd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root inconsistent lock state in valid_state
2024/12/27 12:48 net-next 9268abe611b0 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce inconsistent lock state in valid_state
2024/12/27 10:22 net-next 9268abe611b0 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce inconsistent lock state in valid_state
2024/10/02 10:48 linux-next fe2173353674 ea2b66a6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/09/24 23:45 linux-next 4d0326b60bb7 5643e0e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.