[Android 6.1] invalid opcode in __traceiter_sched_switch

0 views
Skip to first unread message

syzbot

unread,
Apr 26, 2025, 2:10:25 AMApr 26
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 70d648657b1e ANDROID: userfaultfd: adjust MOVE ioctl mode ..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12f94368580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3bbe87affb72322
dashboard link: https://syzkaller.appspot.com/bug?extid=9586fa657641e1a1be2f
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=16f94368580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15664270580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f28bc4d96556/disk-70d64865.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0e86af790fe9/vmlinux-70d64865.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b72580f577c/bzImage-70d64865.xz

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

R10: 0000000000000001 R11: 0000000000000286 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
CFI failure at __traceiter_sched_switch+0x9b/0xd0 include/trace/events/sched.h:222 (target: tp_stub_func+0x0/0x10; expected type: 0xee1f7a69)
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 301 Comm: syz-executor742 Not tainted 6.1.129-syzkaller-00020-g70d648657b1e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:__traceiter_sched_switch+0x9b/0xd0 include/trace/events/sched.h:222
Code: 80 3c 30 00 74 05 e8 a4 47 69 00 49 8b 7d 08 44 89 e6 48 8b 55 c8 48 8b 4d c0 44 8b 45 d4 41 ba 97 85 e0 11 45 03 57 fc 74 02 <0f> 0b 41 ff d7 48 83 c3 18 48 89 d8 48 c1 e8 03 42 80 3c 30 00 74
RSP: 0018:ffffc90000ef7b90 EFLAGS: 00010096
RAX: 1ffff11021e99843 RBX: ffff88810f4cc210 RCX: ffff888125cf8000
RDX: ffff88811e312880 RSI: 0000000000000000 RDI: ffffc900000c9000
RBP: ffffc90000ef7bd0 R08: 0000000000000008 R09: fffffbfff0ee41b6
R10: 00000000b720eca3 R11: 1ffffffff0ee41b5 R12: 0000000000000000
R13: ffff88810f4cc210 R14: dffffc0000000000 R15: ffffffff8170fe20
FS: 000055558c596380(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7c3bb13261 CR3: 0000000124f43000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_sched_switch include/trace/events/sched.h:222 [inline]
__schedule+0x1263/0x14e0 kernel/sched/core.c:6746
schedule+0xbd/0x170 kernel/sched/core.c:6825
ptrace_stop+0x520/0x8b0 kernel/signal.c:2331
ptrace_do_notify kernel/signal.c:2368 [inline]
ptrace_notify+0x1b3/0x250 kernel/signal.c:2380
ptrace_report_syscall include/linux/ptrace.h:420 [inline]
ptrace_report_syscall_exit include/linux/ptrace.h:482 [inline]
syscall_exit_work+0x84/0x140 kernel/entry/common.c:258
syscall_exit_to_user_mode_prepare+0x1c/0x20 kernel/entry/common.c:285
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0xd/0x30 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7c3babdb19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 a1 1a 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffda38bce18 EFLAGS: 00000286 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007ffda38bce30 RCX: 00007f7c3babdb19
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000000
RBP: 0000000000000001 R08: 00007ffda38bcbb7 R09: 0000000000000140
R10: 0000000000000001 R11: 0000000000000286 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__traceiter_sched_switch+0x9b/0xd0 include/trace/events/sched.h:222
Code: 80 3c 30 00 74 05 e8 a4 47 69 00 49 8b 7d 08 44 89 e6 48 8b 55 c8 48 8b 4d c0 44 8b 45 d4 41 ba 97 85 e0 11 45 03 57 fc 74 02 <0f> 0b 41 ff d7 48 83 c3 18 48 89 d8 48 c1 e8 03 42 80 3c 30 00 74
RSP: 0018:ffffc90000ef7b90 EFLAGS: 00010096
RAX: 1ffff11021e99843 RBX: ffff88810f4cc210 RCX: ffff888125cf8000
RDX: ffff88811e312880 RSI: 0000000000000000 RDI: ffffc900000c9000
RBP: ffffc90000ef7bd0 R08: 0000000000000008 R09: fffffbfff0ee41b6
R10: 00000000b720eca3 R11: 1ffffffff0ee41b5 R12: 0000000000000000
R13: ffff88810f4cc210 R14: dffffc0000000000 R15: ffffffff8170fe20
FS: 000055558c596380(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7c3bb13261 CR3: 0000000124f43000 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
Reply all
Reply to author
Forward
0 new messages