[syzbot] [kernel?] WARNING in irqentry_exit (2)

3 views
Skip to first unread message

syzbot

unread,
Aug 4, 2026, 8:13:38 PM (24 hours ago) Aug 4
to linux-...@vger.kernel.org, lu...@kernel.org, pet...@infradead.org, syzkall...@googlegroups.com, tg...@kernel.org
Hello,

syzbot found the following issue on:

HEAD commit: 3708dd948844 Merge tag 'pm-7.2-rc6' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17973632580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f221a1b5d497ed15
dashboard link: https://syzkaller.appspot.com/bug?extid=93cc6b9a8a81c9e47978
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/244376930b41/disk-3708dd94.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6a4fdb2a8dcf/vmlinux-3708dd94.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6d326f1f8ed8/bzImage-3708dd94.xz

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

------------[ cut here ]------------
__lockdep_enabled && this_cpu_read(hardirqs_enabled)
WARNING: ./include/linux/hrtimer_rearm.h:17 at hrtimer_test_and_clear_rearm_deferred_tif include/linux/hrtimer_rearm.h:17 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at hrtimer_rearm_deferred_tif include/linux/hrtimer_rearm.h:52 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at rseq_grant_slice_extension include/linux/rseq_entry.h:236 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at __exit_to_user_mode_loop kernel/entry/common.c:54 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at exit_to_user_mode_loop kernel/entry/common.c:101 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:244 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at irqentry_exit_to_user_mode include/linux/irq-entry-common.h:315 [inline], CPU#0: syz.2.3762/30761
WARNING: ./include/linux/hrtimer_rearm.h:17 at irqentry_exit+0x718/0xa00 kernel/entry/common.c:165, CPU#0: syz.2.3762/30761
Modules linked in:
CPU: 0 UID: 0 PID: 30761 Comm: syz.2.3762 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:hrtimer_test_and_clear_rearm_deferred_tif include/linux/hrtimer_rearm.h:17 [inline]
RIP: 0010:hrtimer_rearm_deferred_tif include/linux/hrtimer_rearm.h:52 [inline]
RIP: 0010:rseq_grant_slice_extension include/linux/rseq_entry.h:236 [inline]
RIP: 0010:__exit_to_user_mode_loop kernel/entry/common.c:54 [inline]
RIP: 0010:exit_to_user_mode_loop kernel/entry/common.c:101 [inline]
RIP: 0010:__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
RIP: 0010:irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:244 [inline]
RIP: 0010:irqentry_exit_to_user_mode include/linux/irq-entry-common.h:315 [inline]
RIP: 0010:irqentry_exit+0x718/0xa00 kernel/entry/common.c:165
Code: 00 00 00 80 e8 c9 ee 58 f6 fb 83 3d 95 d1 69 05 00 74 1a 65 8b 05 d8 2a ab 08 85 c0 75 0f 65 8b 05 29 26 ab 08 85 c0 74 04 90 <0f> 0b 90 41 f7 c5 00 10 00 00 0f 84 74 fc ff ff f0 41 80 64 24 01
RSP: 0000:ffffc9000414ff00 EFLAGS: 00010202
RAX: 0000000000000001 RBX: ffffc9000414ff48 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8e1a8f2e RDI: ffffffff8c400a80
RBP: ffffc9000414ff38 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff888022f39f00
R13: 0000000000000010 R14: 000001efbbd43bba R15: 0000000000000000
FS: 00007f3e64dd56c0(0000) GS:ffff888123de1000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ddddff8 CR3: 0000000034bd6000 CR4: 00000000003526f0
Call Trace:
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:674
RIP: 0033:0x7f3e66b9e019
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:00007f3e64dd50e8 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 00007f3e66e26098 RCX: 00007f3e66b9e019
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f3e66e26098
RBP: 00007f3e66e26090 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3e66e26128 R14: 00007ffe410c4bf0 R15: 00007ffe410c4cd8
</TASK>


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

Peter Zijlstra

unread,
2:16 AM (18 hours ago) 2:16 AM
to syzbot, linux-...@vger.kernel.org, lu...@kernel.org, syzkall...@googlegroups.com, tg...@kernel.org
Reply all
Reply to author
Forward
0 new messages