[v5.15] WARNING in call_timer_fn

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15af9b34180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c170eb20d8be8542
dashboard link: https://syzkaller.appspot.com/bug?extid=17cefe402edee470dda4
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=153a248c180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ac68f24aed3/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8982a3768c5/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb272dd019ce/bzImage-6139f2a0.xz

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

------------[ cut here ]------------
timer: addrconf_rs_timer+0x0/0x610 net/ipv6/addrconf.c:6556 preempt leak: 00000103 -> 00000102
WARNING: CPU: 1 PID: 3537 at kernel/time/timer.c:1428 call_timer_fn+0x29a/0x560 kernel/time/timer.c:1427
Modules linked in:
CPU: 1 PID: 3537 Comm: syz-executor.2 Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:call_timer_fn+0x29a/0x560 kernel/time/timer.c:1427
Code: 11 00 c6 05 83 5f 61 0c 01 65 8b 0d f8 7d 93 7e 81 e1 ff ff ff 7f 48 c7 c7 40 a1 8c 8a 48 8b 74 24 18 44 89 f2 e8 a6 ed dc ff <0f> 0b eb 05 e8 cd 3b 11 00 65 8b 0d ce 7d 93 7e 89 ca 81 e2 00 00
RSP: 0018:ffffc90000dd0ba0 EFLAGS: 00010246
RAX: a5dc8daaec4e4b00 RBX: 0000000000000102 RCX: ffff888073411dc0
RDX: 0000000000000102 RSI: 0000000000000102 RDI: 0000000000000000
RBP: ffffc90000dd0c90 R08: ffffffff81665d9c R09: fffff520001ba0b5
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880733fd6f8
R13: 1ffff920001ba178 R14: 0000000000000103 R15: 00000000ffffbe01
FS: 0000555555e10480(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5f6cb2d1f8 CR3: 0000000023901000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
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:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:196
Code: 00 00 00 0f 1f 00 53 48 89 fb e8 17 00 00 00 48 8b 3d 28 73 63 0c 48 89 de 5b e9 37 df 48 00 cc cc cc cc cc cc cc 48 8b 04 24 <65> 48 8b 0d f4 41 82 7e 65 8b 15 f5 41 82 7e f7 c2 00 01 ff 00 74
RSP: 0018:ffffc90002f16fd8 EFLAGS: 00000287
RAX: ffffffff819649c3 RBX: 000000000000000c RCX: ffffc90002f170a2
RDX: ffff888073411dc0 RSI: 000000000000000c RDI: 0000000000000025
RBP: ffffc90002f17110 R08: ffffffff81964969 R09: 0000000000000004
R10: ffffffffffffffff R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000020 R14: 000000000000000c R15: 0000000000000000
bpf_bprintf_prepare+0x353/0x1310 kernel/bpf/helpers.c:791
____bpf_trace_printk kernel/trace/bpf_trace.c:377 [inline]
bpf_trace_printk+0x140/0x3d0 kernel/trace/bpf_trace.c:368
bpf_prog_cfddb232a7dfb698+0x2f/0x3e0
bpf_dispatcher_nop_func include/linux/bpf.h:776 [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:1883 [inline]
bpf_trace_run3+0x1d1/0x380 kernel/trace/bpf_trace.c:1921
__bpf_trace_kmem_cache_free+0x99/0xc0 include/trace/events/kmem.h:138
__traceiter_kmem_cache_free+0x2e/0x50 include/trace/events/kmem.h:138
trace_kmem_cache_free include/trace/events/kmem.h:138 [inline]
kmem_cache_free+0x1ce/0x1f0 mm/slub.c:3516
merge_or_add_vmap_area mm/vmalloc.c:1142 [inline]
free_vmap_area_noflush+0x899/0x910 mm/vmalloc.c:1759
free_unmap_vmap_area mm/vmalloc.c:1778 [inline]
remove_vm_area+0x1ae/0x1d0 mm/vmalloc.c:2517
vm_remove_mappings mm/vmalloc.c:2546 [inline]
__vunmap+0x325/0xa20 mm/vmalloc.c:2611
__do_replace+0x8ab/0xad0 net/ipv4/netfilter/ip_tables.c:1091
do_replace net/ipv4/netfilter/ip_tables.c:1138 [inline]
do_ipt_set_ctl+0x2cf1/0x3e70 net/ipv4/netfilter/ip_tables.c:1628
nf_setsockopt+0x28a/0x2b0 net/netfilter/nf_sockopt.c:101
ip_setsockopt+0x2732/0x3fb0 net/ipv4/ip_sockglue.c:1442
tcp_setsockopt+0x23f/0x3680 net/ipv4/tcp.c:3694
__sys_setsockopt+0x57e/0x990 net/socket.c:2198
__do_sys_setsockopt net/socket.c:2209 [inline]
__se_sys_setsockopt net/socket.c:2206 [inline]
__x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2206
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
RIP: 0033:0x7f5f6ca2eafa
Code: ff ff ff c3 0f 1f 40 00 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 06 c3 0f 1f 44 00 00 48 c7 c2 b0 ff ff ff f7
RSP: 002b:00007ffe6b75d9f8 EFLAGS: 00000202 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007ffe6b75da80 RCX: 00007f5f6ca2eafa
RDX: 0000000000000040 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000003 R08: 0000000000000240 R09: 00007ffe6b75de37
R10: 00007f5f6cb2d1a0 R11: 0000000000000202 R12: 00007f5f6cb2d140
R13: 00007ffe6b75da1c R14: 0000000000000000 R15: 00007f5f6cb2dec0
</TASK>
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 00 00 add %al,(%rax)
2: 0f 1f 00 nopl (%rax)
5: 53 push %rbx
6: 48 89 fb mov %rdi,%rbx
9: e8 17 00 00 00 call 0x25
e: 48 8b 3d 28 73 63 0c mov 0xc637328(%rip),%rdi # 0xc63733d
15: 48 89 de mov %rbx,%rsi
18: 5b pop %rbx
19: e9 37 df 48 00 jmp 0x48df55
1e: cc int3
1f: cc int3
20: cc int3
21: cc int3
22: cc int3
23: cc int3
24: cc int3
25: 48 8b 04 24 mov (%rsp),%rax
* 29: 65 48 8b 0d f4 41 82 mov %gs:0x7e8241f4(%rip),%rcx # 0x7e824225 <-- trapping instruction
30: 7e
31: 65 8b 15 f5 41 82 7e mov %gs:0x7e8241f5(%rip),%edx # 0x7e82422d
38: f7 c2 00 01 ff 00 test $0xff0100,%edx
3e: 74 .byte 0x74


---
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 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.

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