Hello,
syzbot found the following issue on:
HEAD commit: 1b3143b9b166 UPSTREAM: net: tls, update curr on splice as ..
git tree: android12-5.4
console+strace:
https://syzkaller.appspot.com/x/log.txt?x=1762d058180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=a2dd4b5d39d9fde5
dashboard link:
https://syzkaller.appspot.com/bug?extid=904de93f21b99bec4d00
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=15b36db2180000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=16fc2f68180000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/a095e4f5acb8/disk-1b3143b9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/6ef8e543f489/vmlinux-1b3143b9.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/552a851f1d18/bzImage-1b3143b9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+904de9...@syzkaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 498 Comm: syz-executor320 Not tainted 5.4.265-syzkaller-00001-g1b3143b9b166 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:inherit_group kernel/events/core.c:12068 [inline]
RIP: 0010:inherit_task_group+0x1bf/0x390 kernel/events/core.c:12112
Code: c5 8c 00 00 00 48 89 e8 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 86 01 00 00 8b 5d 00 49 81 c7 8c 00 00 00 4c 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 85 01 00 00 41 89 1f 45 31 ff e9 f4 00
RSP: 0018:ffff8881efbcf9c8 EFLAGS: 00010207
RAX: 0000000000000011 RBX: 0000000000000000 RCX: ffff8881f31dcec0
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff8881f0b67090
RBP: ffff8881f0b6708c R08: dffffc0000000000 R09: ffffed103edeb12c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8881efbcfac0 R14: ffff8881f0b67010 R15: 000000000000008c
FS: 00007fcba5fbc6c0(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001f4dd5000 CR4: 00000000003406a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
perf_event_init_context kernel/events/core.c:12179 [inline]
perf_event_init_task+0x331/0x770 kernel/events/core.c:12231
copy_process+0xf2b/0x3230 kernel/fork.c:2026
_do_fork+0x197/0x900 kernel/fork.c:2399
__do_sys_clone kernel/fork.c:2557 [inline]
__se_sys_clone kernel/fork.c:2538 [inline]
__x64_sys_clone+0x26b/0x2c0 kernel/fork.c:2538
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace 283ff73b2040e566 ]---
RIP: 0010:inherit_group kernel/events/core.c:12068 [inline]
RIP: 0010:inherit_task_group+0x1bf/0x390 kernel/events/core.c:12112
Code: c5 8c 00 00 00 48 89 e8 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 86 01 00 00 8b 5d 00 49 81 c7 8c 00 00 00 4c 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 85 01 00 00 41 89 1f 45 31 ff e9 f4 00
RSP: 0018:ffff8881efbcf9c8 EFLAGS: 00010207
RAX: 0000000000000011 RBX: 0000000000000000 RCX: ffff8881f31dcec0
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff8881f0b67090
RBP: ffff8881f0b6708c R08: dffffc0000000000 R09: ffffed103edeb12c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8881efbcfac0 R14: ffff8881f0b67010 R15: 000000000000008c
FS: 00007fcba5fbc6c0(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcba6074078 CR3: 00000001f4dd5000 CR4: 00000000003406b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 8c 00 mov %es,(%rax)
2: 00 00 add %al,(%rax)
4: 48 89 e8 mov %rbp,%rax
7: 48 c1 e8 03 shr $0x3,%rax
b: 42 0f b6 04 20 movzbl (%rax,%r12,1),%eax
10: 84 c0 test %al,%al
12: 0f 85 86 01 00 00 jne 0x19e
18: 8b 5d 00 mov 0x0(%rbp),%ebx
1b: 49 81 c7 8c 00 00 00 add $0x8c,%r15
22: 4c 89 f8 mov %r15,%rax
25: 48 c1 e8 03 shr $0x3,%rax
* 29: 42 0f b6 04 20 movzbl (%rax,%r12,1),%eax <-- trapping instruction
2e: 84 c0 test %al,%al
30: 0f 85 85 01 00 00 jne 0x1bb
36: 41 89 1f mov %ebx,(%r15)
39: 45 31 ff xor %r15d,%r15d
3c: e9 .byte 0xe9
3d: f4 hlt
---
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