[v5.15] WARNING in call_timer_fn (2)

Hello,

syzbot found the following issue on:

HEAD commit: a68c15152131 Linux 5.15.183
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15f5de70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef02e502f5873d8
dashboard link: https://syzkaller.appspot.com/bug?extid=97c9d96f4cf6e2f67ce5
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9057058298cc/disk-a68c1515.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3e83bf000c3a/vmlinux-a68c1515.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6809226eafd9/bzImage-a68c1515.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5521 at kernel/workqueue.c:1453 __queue_work+0xc04/0xd50 kernel/workqueue.c:1453
Modules linked in:
CPU: 1 PID: 5521 Comm: syz.5.304 Not tainted 5.15.183-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:__queue_work+0xc04/0xd50 kernel/workqueue.c:1453
Code: fc ff ff 48 8b 4c 24 08 80 e1 07 80 c1 03 38 c1 0f 8c 13 fd ff ff 48 8b 7c 24 08 e8 56 32 70 00 e9 04 fd ff ff e8 2c bf 2a 00 <0f> 0b 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 16 bf 2a 00
RSP: 0018:ffffc90000dd0b18 EFLAGS: 00010046
RAX: ffffffff814d0214 RBX: 0000000000010000 RCX: ffff888027121dc0
RDX: 0000000000000100 RSI: 0000000000000100 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1ad148e
R10: fffffbfff1ad148e R11: 1ffffffff1ad148d R12: ffff88801a9e2180
R13: ffff88807e0179c0 R14: ffff88807e017800 R15: 0000000000000008
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13771ab4e8 CR3: 000000000be8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
call_timer_fn+0x16c/0x530 kernel/time/timer.c:1451
expire_timers kernel/time/timer.c:1491 [inline]
__run_timers+0x550/0x7c0 kernel/time/timer.c:1767
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1780
handle_softirqs+0x328/0x820 kernel/softirq.c:558
__do_softirq kernel/softirq.c:592 [inline]
invoke_softirq kernel/softirq.c:432 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:641
irq_exit_rcu+0x5/0x20 kernel/softirq.c:653
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:instrument_atomic_read include/linux/instrumented.h:71 [inline]
RIP: 0010:atomic_read include/linux/atomic/atomic-instrumented.h:27 [inline]
RIP: 0010:lock_page_memcg+0x20c/0x410 mm/memcontrol.c:2064
Code: ff 48 c7 44 24 40 00 00 00 00 9c 8f 44 24 40 f6 44 24 41 02 0f 85 f9 00 00 00 f7 c3 00 02 00 00 74 01 fb 4d 8d af 80 10 00 00 <4c> 89 ef be 04 00 00 00 e8 f7 95 fb ff 4c 89 e8 48 c1 e8 03 48 b9
RSP: 0018:ffffc9000346f420 EFLAGS: 00000206
RAX: 1e78c0e9f8326f00 RBX: 0000000000000286 RCX: 1e78c0e9f8326f00
RDX: dffffc0000000000 RSI: ffffffff8a0b0fc0 RDI: ffffffff8a59a2c0
RBP: ffffc9000346f4f8 R08: dffffc0000000000 R09: fffffbfff1ff3219
R10: fffffbfff1ff3219 R11: 1ffffffff1ff3218 R12: ffff88814077c670
R13: ffff88814077d080 R14: ffffea00014a0ff8 R15: ffff88814077c000
page_remove_rmap+0x2a/0x10f0 mm/rmap.c:1351
zap_pte_range mm/memory.c:1384 [inline]
zap_pmd_range mm/memory.c:1505 [inline]
zap_pud_range mm/memory.c:1534 [inline]
zap_p4d_range mm/memory.c:1555 [inline]
unmap_page_range+0xfbc/0x2520 mm/memory.c:1576
unmap_vmas+0x11b/0x230 mm/memory.c:1653
exit_mmap+0x38f/0x5f0 mm/mmap.c:3204
__mmput+0x115/0x3b0 kernel/fork.c:1127
exit_mm+0x567/0x6c0 kernel/exit.c:550
do_exit+0x599/0x20a0 kernel/exit.c:861
do_group_exit+0x12e/0x300 kernel/exit.c:996
get_signal+0x6ca/0x12c0 kernel/signal.c:2900
arch_do_signal_or_restart+0xc1/0x1300 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7efe8200d969
Code: Unable to access opcode bytes at RIP 0x7efe8200d93f.
RSP: 002b:00007efe7fe54038 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: 0000000000010106 RBX: 00007efe82235080 RCX: 00007efe8200d969
RDX: 0000000000010106 RSI: 00002000000000c0 RDI: 0000000000000003
RBP: 00007efe8208fab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007efe82235080 R15: 00007ffd69f6bec8
</TASK>
----------------
Code disassembly (best guess):
0: ff 48 c7 decl -0x39(%rax)
3: 44 24 40 rex.R and $0x40,%al
6: 00 00 add %al,(%rax)
8: 00 00 add %al,(%rax)
a: 9c pushf
b: 8f 44 24 40 pop 0x40(%rsp)
f: f6 44 24 41 02 testb $0x2,0x41(%rsp)
14: 0f 85 f9 00 00 00 jne 0x113
1a: f7 c3 00 02 00 00 test $0x200,%ebx
20: 74 01 je 0x23
22: fb sti
23: 4d 8d af 80 10 00 00 lea 0x1080(%r15),%r13
* 2a: 4c 89 ef mov %r13,%rdi <-- trapping instruction
2d: be 04 00 00 00 mov $0x4,%esi
32: e8 f7 95 fb ff call 0xfffb962e
37: 4c 89 e8 mov %r13,%rax
3a: 48 c1 e8 03 shr $0x3,%rax
3e: 48 rex.W
3f: b9 .byte 0xb9


---
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 [email protected].

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