inconsistent lock state in trie_delete_elem

Status: upstream: reported C repro on 2025/12/04 17:55
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+644bfebcf8f53278b7e5@syzkaller.appspotmail.com
First crash: 267d, last: 2h32m
Bug presence (2)
Date Name Commit Repro Result
2025/12/05 linux-5.15.y (ToT) cc5ec8769306 C [report] inconsistent lock state in trie_delete_elem
2025/12/05 upstream (ToT) 7203ca412fc8 C Didn't crash
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 inconsistent lock state in trie_delete_elem origin:lts-only 4 syz, C inconclusive 81 1d12h 267d 0/3 upstream: reported C repro on 2025/12/04 16:53
linux-6.6 inconsistent lock state in trie_delete_elem origin:lts-only 4 syz, C inconclusive 93 5d07h 266d 0/2 upstream: reported C repro on 2025/12/04 20:31
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2026/04/26 04:31 37m fix candidate upstream error job log
2026/03/24 00:20 1h30m fix candidate upstream error job log
2026/02/21 07:21 7m fix candidate upstream error job log
2026/01/21 17:52 3m fix candidate upstream error job log

Sample crash report:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {INITIAL USE} -> {IN-NMI} usage.
syz.0.17/4318 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffff88801fd72a38 (&trie->lock){....}-{2:2}, at: trie_delete_elem+0x8e/0x620 kernel/bpf/lpm_trie.c:466
{INITIAL USE} state was registered at:
  lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
  __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
  _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162
  trie_delete_elem+0x8e/0x620 kernel/bpf/lpm_trie.c:466
  bpf_prog_1db1603a7cfa36fb+0x3d/0xec4
  bpf_dispatcher_nop_func include/linux/bpf.h:889 [inline]
  __bpf_prog_run include/linux/filter.h:628 [inline]
  bpf_prog_run include/linux/filter.h:635 [inline]
  bpf_overflow_handler+0x1c2/0x4a0 kernel/events/core.c:10297
  __perf_event_overflow+0x35f/0x550 kernel/events/core.c:9515
  perf_bp_event+0x276/0x320 kernel/events/core.c:10484
  hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
  hw_breakpoint_exceptions_notify+0x14d/0x470 arch/x86/kernel/hw_breakpoint.c:586
  notifier_call_chain kernel/notifier.c:83 [inline]
  atomic_notifier_call_chain+0x15d/0x280 kernel/notifier.c:198
  notify_die+0x141/0x1a0 kernel/notifier.c:529
  notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
  exc_debug_user arch/x86/kernel/traps.c:998 [inline]
  noist_exc_debug+0x73/0x120 arch/x86/kernel/traps.c:1035
  asm_exc_debug+0x2f/0x40 arch/x86/include/asm/idtentry.h:642
irq event stamp: 10766
hardirqs last  enabled at (10765): [<ffffffff89c09fc1>] syscall_enter_from_user_mode+0x21/0x70 kernel/entry/common.c:113
hardirqs last disabled at (10766): [<ffffffff89c0703e>] exc_debug_kernel arch/x86/kernel/traps.c:893 [inline]
hardirqs last disabled at (10766): [<ffffffff89c0703e>] exc_debug+0x6e/0x130 arch/x86/kernel/traps.c:1029
softirqs last  enabled at (10724): [<ffffffff8186ad3e>] bpf_prog_load+0x10ee/0x14e0 kernel/bpf/syscall.c:2380
softirqs last disabled at (10722): [<ffffffff81851008>] spin_lock_bh include/linux/spinlock.h:369 [inline]
softirqs last disabled at (10722): [<ffffffff81851008>] bpf_ksym_add+0x28/0x330 kernel/bpf/core.c:633

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

       CPU0
       ----
  lock(&trie->lock);
  <Interrupt>
    lock(&trie->lock);

 *** DEADLOCK ***

no locks held by syz.0.17/4318.

stack backtrace:
CPU: 0 PID: 4318 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <#DB>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 lock_acquire+0x2c3/0x400 kernel/locking/lockdep.c:5614
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162
 trie_delete_elem+0x8e/0x620 kernel/bpf/lpm_trie.c:466
 bpf_prog_1db1603a7cfa36fb+0x3d/0xec4
 bpf_dispatcher_nop_func include/linux/bpf.h:889 [inline]
 __bpf_prog_run include/linux/filter.h:628 [inline]
 bpf_prog_run include/linux/filter.h:635 [inline]
 bpf_overflow_handler+0x1c2/0x4a0 kernel/events/core.c:10297
 __perf_event_overflow+0x35f/0x550 kernel/events/core.c:9515
 perf_bp_event+0x276/0x320 kernel/events/core.c:10484
 hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
 hw_breakpoint_exceptions_notify+0x14d/0x470 arch/x86/kernel/hw_breakpoint.c:586
 notifier_call_chain kernel/notifier.c:83 [inline]
 atomic_notifier_call_chain+0x15d/0x280 kernel/notifier.c:198
 notify_die+0x141/0x1a0 kernel/notifier.c:529
 notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
 exc_debug_kernel arch/x86/kernel/traps.c:929 [inline]
 exc_debug+0xcf/0x130 arch/x86/kernel/traps.c:1029
 asm_exc_debug+0x1a/0x40 arch/x86/include/asm/idtentry.h:642
RIP: 0010:copy_user_generic_unrolled+0x89/0xc0 arch/x86/lib/copy_user_64.S:92
Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
RSP: 0018:ffffc9000315fd80 EFLAGS: 00040202
RAX: ffffffff83e87b01 RBX: 0000000000000020 RCX: 0000000000000004
RDX: 0000000000000000 RSI: 0000200000000300 RDI: ffffc9000315fe00
RBP: 0000000000000000 R08: 0000000affffffff R09: 1ffff9200062bfc3
R10: dffffc0000000000 R11: fffff5200062bfc4 R12: 00007ffffffff000
R13: 0000200000000320 R14: ffffc9000315fe00 R15: 0000200000000300
 </#DB>
 <TASK>
 copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
 raw_copy_from_user arch/x86/include/asm/uaccess_64.h:52 [inline]
 _copy_from_user+0xfa/0x170 lib/usercopy.c:23
 copy_from_user include/linux/uaccess.h:192 [inline]
 copy_from_bpfptr_offset include/linux/bpfptr.h:52 [inline]
 copy_from_bpfptr include/linux/bpfptr.h:58 [inline]
 __sys_bpf+0x26d/0x6f0 kernel/bpf/syscall.c:4630
 __do_sys_bpf kernel/bpf/syscall.c:4761 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:4759 [inline]
 __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4759
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f99b71d80d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc0ffc3618 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f99b745ffa0 RCX: 00007f99b71d80d9
RDX: 0000000000000020 RSI: 0000200000000300 RDI: 0000000000000009
RBP: 00007f99b726f024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f99b745ffac R14: 00007f99b745ffa0 R15: 00007f99b745ffa0
 </TASK>
----------------
Code disassembly (best guess):
   0:	38 4c 89 47          	cmp    %cl,0x47(%rcx,%rcx,4)
   4:	20 4c 89 4f          	and    %cl,0x4f(%rcx,%rcx,4)
   8:	28 4c 89 57          	sub    %cl,0x57(%rcx,%rcx,4)
   c:	30 4c 89 5f          	xor    %cl,0x5f(%rcx,%rcx,4)
  10:	38 48 8d             	cmp    %cl,-0x73(%rax)
  13:	76 40                	jbe    0x55
  15:	48 8d 7f 40          	lea    0x40(%rdi),%rdi
  19:	ff c9                	dec    %ecx
  1b:	75 b6                	jne    0xffffffd3
  1d:	89 d1                	mov    %edx,%ecx
  1f:	83 e2 07             	and    $0x7,%edx
  22:	c1 e9 03             	shr    $0x3,%ecx
  25:	74 12                	je     0x39
  27:	4c 8b 06             	mov    (%rsi),%r8
* 2a:	4c 89 07             	mov    %r8,(%rdi) <-- trapping instruction
  2d:	48 8d 76 08          	lea    0x8(%rsi),%rsi
  31:	48 8d 7f 08          	lea    0x8(%rdi),%rdi
  35:	ff c9                	dec    %ecx
  37:	75 ee                	jne    0x27
  39:	21 d2                	and    %edx,%edx
  3b:	74 10                	je     0x4d
  3d:	89 d1                	mov    %edx,%ecx
  3f:	8a                   	.byte 0x8a

Crashes (1398):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/23 08:37 linux-5.15.y 0eb903b5b519 1e72964b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/12 22:19 linux-5.15.y aabd761612db 359b2492 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/26 23:57 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/01/16 16:01 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2025/12/04 19:07 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2025/12/04 17:54 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/05 04:20 linux-5.15.y ef251c45f1cd a898ba9c .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/04 14:54 linux-5.15.y ef251c45f1cd 85f1bcf2 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/01/15 14:20 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/28 17:51 linux-5.15.y 28c35638ec51 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/28 15:48 linux-5.15.y 28c35638ec51 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 23:57 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 22:54 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 21:48 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 20:39 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 19:35 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 09:03 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 05:34 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 04:59 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 02:48 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/27 00:02 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/26 17:58 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/26 16:50 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/26 12:21 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/26 10:01 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/26 06:47 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 23:56 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 22:13 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 10:40 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 09:18 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 08:07 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 03:58 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/25 01:45 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 22:25 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 20:47 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 17:00 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 15:51 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 09:30 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 08:09 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 06:52 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 05:46 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 04:43 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 03:15 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 02:47 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/24 01:08 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 23:05 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 21:16 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 20:14 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 17:20 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 15:53 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 10:04 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 06:51 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 06:37 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 05:25 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 04:23 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 03:01 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/23 01:16 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/22 22:54 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/08/22 21:57 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
* Struck through repros no longer work on HEAD.