[Android 6.1] invalid opcode in __traceiter_timer_start

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 25fc41bbde8e ANDROID: GKI: Update symbol list for mtk
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13f41d74580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3bbe87affb72322
dashboard link: https://syzkaller.appspot.com/bug?extid=5566b966cd8fbf668767
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11fec270580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163cc368580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fde4042d6828/disk-25fc41bb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/56abc23b4bed/vmlinux-25fc41bb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/247ff7527f1e/bzImage-25fc41bb.xz

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

CFI failure at __traceiter_timer_start+0x87/0xe0 include/trace/events/timer.h:53 (target: tp_stub_func+0x0/0x10; expected type: 0x82fbfa63)
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 14 Comm: rcu_preempt Not tainted 6.1.129-syzkaller-00022-g25fc41bbde8e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:__traceiter_timer_start+0x87/0xe0 include/trace/events/timer.h:53
Code: f8 48 c1 e8 03 80 3c 18 00 74 05 e8 43 3d 53 00 49 8b 7d 08 4c 89 fe 48 8b 55 c8 8b 4d d4 41 ba 9d 05 04 7d 45 03 56 fc 74 02 <0f> 0b 41 ff d6 49 83 c4 18 4c 89 e0 48 c1 e8 03 80 3c 18 00 74 08
RSP: 0018:ffffc900000e7ac0 EFLAGS: 00010017

RAX: 1ffff11021ca0086 RBX: dffffc0000000000 RCX: 000000000f800000
RDX: 00000000ffff93fd RSI: ffffc900000e7c20 RDI: ffffc900000f9000
RBP: ffffc900000e7af8 R08: dffffc0000000000 R09: ffffc900000e7988
R10: 0000000022446ca9 R11: 1ffff9200001cf31 R12: ffff88810e500428
R13: ffff88810e500428 R14: ffffffff8170fe20 R15: ffffc900000e7c20
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001100e5000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_timer_start include/trace/events/timer.h:53 [inline]
enqueue_timer+0x337/0x480 kernel/time/timer.c:615
__mod_timer+0x79f/0xb30 kernel/time/timer.c:-1
schedule_timeout+0x127/0x2e0 kernel/time/timer.c:1970
rcu_gp_fqs_loop+0x2d8/0x10a0 kernel/rcu/tree.c:1706
rcu_gp_kthread+0x95/0x370 kernel/rcu/tree.c:1905
kthread+0x281/0x320 kernel/kthread.c:386
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__traceiter_timer_start+0x87/0xe0 include/trace/events/timer.h:53
Code: f8 48 c1 e8 03 80 3c 18 00 74 05 e8 43 3d 53 00 49 8b 7d 08 4c 89 fe 48 8b 55 c8 8b 4d d4 41 ba 9d 05 04 7d 45 03 56 fc 74 02 <0f> 0b 41 ff d6 49 83 c4 18 4c 89 e0 48 c1 e8 03 80 3c 18 00 74 08
RSP: 0018:ffffc900000e7ac0 EFLAGS: 00010017

RAX: 1ffff11021ca0086 RBX: dffffc0000000000 RCX: 000000000f800000
RDX: 00000000ffff93fd RSI: ffffc900000e7c20 RDI: ffffc900000f9000
RBP: ffffc900000e7af8 R08: dffffc0000000000 R09: ffffc900000e7988
R10: 0000000022446ca9 R11: 1ffff9200001cf31 R12: ffff88810e500428
R13: ffff88810e500428 R14: ffffffff8170fe20 R15: ffffc900000e7c20
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001100e5000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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