[v5.15] inconsistent lock state in valid_state (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 574362648507 Linux 5.15.151
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156e5859180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6c9a42d9e3519ca9
dashboard link: https://syzkaller.appspot.com/bug?extid=db6a6f32b60f325125ab
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f00d4062000b/disk-57436264.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3a74c2b6ca62/vmlinux-57436264.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93bd706dc219/bzImage-57436264.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+db6a6f...@syzkaller.appspotmail.com

================================
WARNING: inconsistent lock state
5.15.151-syzkaller #0 Not tainted
--------------------------------
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
syz-executor.2/15030 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffffffff8d14d958 (sync_timeline_list_lock){?.+.}-{2:2}, at: sync_timeline_debug_remove+0x28/0x140 drivers/dma-buf/sync_debug.c:31
{HARDIRQ-ON-W} state was registered at:
trace_hardirqs_on+0x67/0x80 kernel/trace/trace_preemptirq.c:49
__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:168 [inline]
_raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202
spin_unlock_irq include/linux/spinlock.h:413 [inline]
sync_print_obj drivers/dma-buf/sync_debug.c:118 [inline]
sync_info_debugfs_show+0x154/0x4c0 drivers/dma-buf/sync_debug.c:153
seq_read_iter+0x43a/0xd10 fs/seq_file.c:230
seq_read+0x452/0x5c0 fs/seq_file.c:162
do_iter_read+0x4ca/0x760 fs/read_write.c:792
vfs_readv fs/read_write.c:910 [inline]
do_preadv+0x211/0x350 fs/read_write.c:1002
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
irq event stamp: 502
hardirqs last enabled at (501): [<ffffffff8a25268f>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:168 [inline]
hardirqs last enabled at (501): [<ffffffff8a25268f>] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202
hardirqs last disabled at (502): [<ffffffff8a1b890a>] sysvec_irq_work+0xa/0xb0 arch/x86/kernel/irq_work.c:17
softirqs last enabled at (406): [<ffffffff814d64f5>] invoke_softirq kernel/softirq.c:432 [inline]
softirqs last enabled at (406): [<ffffffff814d64f5>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:637
softirqs last disabled at (293): [<ffffffff814d64f5>] invoke_softirq kernel/softirq.c:432 [inline]
softirqs last disabled at (293): [<ffffffff814d64f5>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:637

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-executor.2/15030.

stack backtrace:
CPU: 1 PID: 15030 Comm: syz-executor.2 Not tainted 5.15.151-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
valid_state+0x134/0x1c0 kernel/locking/lockdep.c:3932
mark_lock_irq+0xa8/0xba0 kernel/locking/lockdep.c:4135
mark_lock+0x21a/0x340 kernel/locking/lockdep.c:4591
mark_usage kernel/locking/lockdep.c:4483 [inline]
__lock_acquire+0xb5c/0x1ff0 kernel/locking/lockdep.c:4966
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
sync_timeline_debug_remove+0x28/0x140 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+0x200/0x250 drivers/dma-buf/sw_sync.c:144
kref_put include/linux/kref.h:65 [inline]
dma_fence_put include/linux/dma-fence.h:279 [inline]
dma_fence_array_release+0x127/0x230 drivers/dma-buf/dma-fence-array.c:120
irq_work_single kernel/irq_work.c:155 [inline]
irq_work_run_list+0x20b/0x370 kernel/irq_work.c:177
irq_work_run+0x63/0xe0 kernel/irq_work.c:186
__sysvec_irq_work+0x9a/0x250 arch/x86/kernel/irq_work.c:22
sysvec_irq_work+0x89/0xb0 arch/x86/kernel/irq_work.c:17
</IRQ>
<TASK>
asm_sysvec_irq_work+0x16/0x20 arch/x86/include/asm/idtentry.h:664
RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:169 [inline]
RIP: 0010:_raw_spin_unlock_irq+0x25/0x40 kernel/locking/spinlock.c:202
Code: 81 82 f6 ff 90 53 48 89 fb 48 83 c7 18 48 8b 74 24 08 e8 ee 86 3d f7 48 89 df e8 c6 da 3e f7 e8 e1 8c 61 f7 fb bf 01 00 00 00 <e8> f6 16 32 f7 65 8b 05 27 49 dd 75 85 c0 74 02 5b c3 e8 b4 60 db
RSP: 0018:ffffc90004877d88 EFLAGS: 00000282
RAX: 2314e96600071b00 RBX: ffff888029ed1750 RCX: ffffffff913c6f03
RDX: dffffc0000000000 RSI: ffffffff8a8b1500 RDI: 0000000000000001
RBP: ffff88802325a43c R08: ffffffff8186b3a0 R09: ffffed10053da2eb
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888029ed1740
R13: ffff88802325a400 R14: dffffc0000000000 R15: ffff888029ed1700
spin_unlock_irq include/linux/spinlock.h:413 [inline]
sw_sync_debugfs_release+0x145/0x1c0 drivers/dma-buf/sw_sync.c:321
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fcad7011da9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcad55920c8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fcad713ff80 RCX: 00007fcad7011da9
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000003
RBP: 00007fcad705e47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fcad713ff80 R15: 00007ffcab853858
</TASK>
----------------
Code disassembly (best guess):
0: 81 82 f6 ff 90 53 48 addl $0x48fb8948,0x5390fff6(%rdx)
7: 89 fb 48
a: 83 c7 18 add $0x18,%edi
d: 48 8b 74 24 08 mov 0x8(%rsp),%rsi
12: e8 ee 86 3d f7 call 0xf73d8705
17: 48 89 df mov %rbx,%rdi
1a: e8 c6 da 3e f7 call 0xf73edae5
1f: e8 e1 8c 61 f7 call 0xf7618d05
24: fb sti
25: bf 01 00 00 00 mov $0x1,%edi
* 2a: e8 f6 16 32 f7 call 0xf7321725 <-- trapping instruction
2f: 65 8b 05 27 49 dd 75 mov %gs:0x75dd4927(%rip),%eax # 0x75dd495d
36: 85 c0 test %eax,%eax
38: 74 02 je 0x3c
3a: 5b pop %rbx
3b: c3 ret
3c: e8 .byte 0xe8
3d: b4 60 mov $0x60,%ah
3f: db .byte 0xdb


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: b95c01af2113 Linux 5.15.152
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17b11a6e180000
kernel config: https://syzkaller.appspot.com/x/.config?x=b26cb65e5b8ad5c7

dashboard link: https://syzkaller.appspot.com/bug?extid=db6a6f32b60f325125ab
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c6edc9180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13901aa5180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2fc98856fcae/disk-b95c01af.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3186db0dfe08/vmlinux-b95c01af.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0df136a3e808/bzImage-b95c01af.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+db6a6f...@syzkaller.appspotmail.com

================================
WARNING: inconsistent lock state

5.15.152-syzkaller #0 Not tainted
--------------------------------
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
syz-executor908/3501 [HC0[0]:SC1[1]:HE0:SE0] takes:
ffff8880b9b28098 (&base->lock){?.-.}-{2:2}, at: lock_timer_base+0x120/0x260 kernel/time/timer.c:946
{IN-HARDIRQ-W} state was registered at:

lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162

lock_timer_base+0x120/0x260 kernel/time/timer.c:946
add_timer_on+0x1eb/0x580 kernel/time/timer.c:1169
handle_irq_event_percpu kernel/irq/handle.c:198 [inline]
handle_irq_event+0x124/0x2b0 kernel/irq/handle.c:213
handle_level_irq+0x3ab/0x6c0 kernel/irq/chip.c:653
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq arch/x86/kernel/irq.c:231 [inline]
__common_interrupt+0xd7/0x1f0 arch/x86/kernel/irq.c:250
common_interrupt+0x9f/0xc0 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x22/0x40 arch/x86/include/asm/idtentry.h:629
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
_raw_spin_unlock_irqrestore+0xd4/0x130 kernel/locking/spinlock.c:194
__setup_irq+0x1302/0x1d90 kernel/irq/manage.c:1817
request_threaded_irq+0x2a7/0x380 kernel/irq/manage.c:2206
request_irq include/linux/interrupt.h:168 [inline]
setup_default_timer_irq+0x1f/0x30 arch/x86/kernel/time.c:70
x86_late_time_init+0x51/0x86 arch/x86/kernel/time.c:94
start_kernel+0x40a/0x535 init/main.c:1100
secondary_startup_64_no_verify+0xb1/0xbb
irq event stamp: 1001
hardirqs last enabled at (1000): [<ffffffff8a25468f>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:168 [inline]
hardirqs last enabled at (1000): [<ffffffff8a25468f>] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202
hardirqs last disabled at (1001): [<ffffffff8a25433c>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (1001): [<ffffffff8a25433c>] _raw_spin_lock_irqsave+0xac/0x120 kernel/locking/spinlock.c:162
softirqs last enabled at (962): [<ffffffff818e10fd>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (962): [<ffffffff818e10fd>] bpf_link_settle+0x7d/0x140 kernel/bpf/syscall.c:2590
softirqs last disabled at (997): [<ffffffff814d64f5>] invoke_softirq kernel/softirq.c:432 [inline]
softirqs last disabled at (997): [<ffffffff814d64f5>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:637

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

CPU0
----

lock(&base->lock
);
<Interrupt>
lock(&base->lock
);

*** DEADLOCK ***

6 locks held by syz-executor908/3501:
#0: ffff88801997b928
(&mm->mmap_lock
){++++}-{3:3}
, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
, at: do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
, at: handle_page_fault arch/x86/mm/fault.c:1485 [inline]
, at: exc_page_fault+0x181/0x740 arch/x86/mm/fault.c:1541
#1: ffffffff8c91f720
(rcu_read_lock
){....}-{1:2}
, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:268
#2: ffffc90000dd0be0
((&dsp_spl_tl)
){+.-.}-{0:0}
, at: lockdep_copy_map include/linux/lockdep.h:45 [inline]
, at: call_timer_fn+0xbe/0x560 kernel/time/timer.c:1411
#3: ffffffff8d798d18
(dsp_lock
){+.-.}-{2:2}, at: dsp_cmx_send+0x22/0x2240 drivers/isdn/mISDN/dsp_cmx.c:1643
#4: ffff8880b9b28098
(&base->lock
){?.-.}-{2:2}
, at: lock_timer_base+0x120/0x260 kernel/time/timer.c:946
#5: ffffffff8c91f720
(rcu_read_lock
){....}-{1:2}
, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:268

stack backtrace:
CPU: 1 PID: 3501 Comm: syz-executor908 Not tainted 5.15.152-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
valid_state+0x134/0x1c0 kernel/locking/lockdep.c:3932
mark_lock_irq+0xa8/0xba0 kernel/locking/lockdep.c:4135
mark_lock+0x21a/0x340 kernel/locking/lockdep.c:4591

mark_held_locks kernel/locking/lockdep.c:4193 [inline]
__trace_hardirqs_on_caller kernel/locking/lockdep.c:4211 [inline]
lockdep_hardirqs_on_prepare+0x27d/0x7a0 kernel/locking/lockdep.c:4278
trace_hardirqs_on+0x67/0x80 kernel/trace/trace_preemptirq.c:49
__local_bh_enable_ip+0x164/0x1f0 kernel/softirq.c:388
sock_hash_delete_elem+0x1a0/0x2f0 net/core/sock_map.c:945
bpf_prog_6f5f05285f674219+0x3a/0xf28
bpf_dispatcher_nop_func include/linux/bpf.h:780 [inline]
__bpf_prog_run include/linux/filter.h:625 [inline]
bpf_prog_run include/linux/filter.h:632 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1880 [inline]
bpf_trace_run3+0x1d1/0x380 kernel/trace/bpf_trace.c:1918
trace_timer_start include/trace/events/timer.h:52 [inline]
enqueue_timer+0x3ae/0x540 kernel/time/timer.c:586
internal_add_timer kernel/time/timer.c:611 [inline]
__mod_timer+0xa60/0xeb0 kernel/time/timer.c:1062
dsp_cmx_send+0x21bb/0x2240 drivers/isdn/mISDN/dsp_cmx.c:1850
call_timer_fn+0x16d/0x560 kernel/time/timer.c:1421
expire_timers kernel/time/timer.c:1466 [inline]
__run_timers+0x67c/0x890 kernel/time/timer.c:1737
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1750
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
invoke_softirq kernel/softirq.c:432 [inline]
__irq_exit_rcu+0x155/0x240 kernel/softirq.c:637
irq_exit_rcu+0x5/0x20 kernel/softirq.c:649
sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:check_preemption_disabled+0x19/0x110 lib/smp_processor_id.c:14
Code: cc 48 c7 c7 a0 8e d8 8a 48 c7 c6 e0 8e d8 8a eb 00 41 57 41 56 41 54 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 <65> 8b 1d 68 38 e6 75 65 8b 05 d1 92 e6 75 a9 ff ff ff 7f 74 22 65
RSP: 0000:ffffc900011dfad8 EFLAGS: 00000286
RAX: 0a87c466efc75300 RBX: 0000000000000000 RCX: ffff888078b7bb80
RDX: ffff888078b7bb80 RSI: ffffffff8ad88ee0 RDI: ffffffff8ad88ea0
RBP: ffffc900011dfc10 R08: ffffffff81b8dde7 R09: fffffbfff1f79e19
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000014
R13: dffffc0000000000 R14: 1ffff9200023bf6c R15: ffff888078b7bb80
rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:331 [inline]
rcu_is_watching+0x11/0xa0 kernel/rcu/tree.c:1123
rcu_read_lock_held_common kernel/rcu/update.c:108 [inline]
rcu_read_lock_held+0x11/0x40 kernel/rcu/update.c:309
count_memcg_event_mm+0x145/0x3e0 include/linux/memcontrol.h:1079
handle_mm_fault+0x161/0x5950 mm/memory.c:4834
do_user_addr_fault arch/x86/mm/fault.c:1397 [inline]
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0033:0x7f0ac813e178
Code: Unable to access opcode bytes at RIP 0x7f0ac813e14e.
RSP: 002b:00007ffc688f8628 EFLAGS: 00010206
RAX: 00007f0ac816ead8 RBX: 0000000000000000 RCX: 0000000000000004
RDX: 00007f0ac816fd00 RSI: 0000000000000000 RDI: 00007f0ac816ead8
RBP: 00007f0ac816d118 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f0ac816fce8
R13: 0000000000000000 R14: 00007f0ac816fd00 R15: 00007f0ac80c5160
</TASK>
------------[ cut here ]------------
raw_local_irq_restore() called with IRQs enabled
WARNING: CPU: 1 PID: 3501 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Modules linked in:

CPU: 1 PID: 3501 Comm: syz-executor908 Not tainted 5.15.152-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024

RIP: 0010:warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Code: 24 48 c7 c7 a0 d1 89 8a e8 6c d1 fe ff 80 3d ae 7f b4 03 00 74 01 c3 c6 05 a4 7f b4 03 01 48 c7 c7 80 0c 8b 8a e8 f3 1b 30 f7 <0f> 0b c3 41 56 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44
RSP: 0000:ffffc90000dd0898 EFLAGS: 00010246

RAX: 0a87c466efc75300 RBX: 1ffff920001ba118 RCX: ffff888078b7bb80
RDX: 0000000000000103 RSI: 0000000000000103 RDI: 0000000000000000
RBP: ffffc90000dd0930 R08: ffffffff8166665c R09: fffffbfff1922849
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff920001ba114 R14: ffffc90000dd08c0 R15: 0000000000000046
FS: 0000555555e3c380(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0ac813e14e CR3: 000000001a390000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
_raw_spin_unlock_irqrestore+0x118/0x130 kernel/locking/spinlock.c:194
__mod_timer+0xa8e/0xeb0 kernel/time/timer.c:1065

----------------
Code disassembly (best guess):

0: cc int3
1: 48 c7 c7 a0 8e d8 8a mov $0xffffffff8ad88ea0,%rdi
8: 48 c7 c6 e0 8e d8 8a mov $0xffffffff8ad88ee0,%rsi
f: eb 00 jmp 0x11
11: 41 57 push %r15
13: 41 56 push %r14
15: 41 54 push %r12
17: 53 push %rbx
18: 48 83 ec 10 sub $0x10,%rsp
1c: 65 48 8b 04 25 28 00 mov %gs:0x28,%rax
23: 00 00
25: 48 89 44 24 08 mov %rax,0x8(%rsp)
* 2a: 65 8b 1d 68 38 e6 75 mov %gs:0x75e63868(%rip),%ebx # 0x75e63899 <-- trapping instruction
31: 65 8b 05 d1 92 e6 75 mov %gs:0x75e692d1(%rip),%eax # 0x75e69309
38: a9 ff ff ff 7f test $0x7fffffff,%eax
3d: 74 22 je 0x61
3f: 65 gs


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.