Hello,
syzbot found the following issue on:
HEAD commit: f67653019430 Linux 5.15.118
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=117c69e0a80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c6daef03436a2bc5
dashboard link:
https://syzkaller.appspot.com/bug?extid=e5389639a271451d71c8
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/600ef9372d32/disk-f6765301.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/46dca37198b3/vmlinux-f6765301.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/7ae4a35a0a6d/Image-f6765301.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+e53896...@syzkaller.appspotmail.com
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
------------[ cut here ]------------
WARNING: CPU: 1 PID: 20848 at net/ipv6/ip6_fib.c:1506 fib6_add+0x26fc/0x3400
Modules linked in:
CPU: 1 PID: 20848 Comm: syz-executor.1 Not tainted 5.15.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : fib6_add+0x26fc/0x3400
lr : fib6_add+0x26fc/0x3400
sp : ffff80001ec57500
x29: ffff80001ec576e0 x28: ffff000123a6d800 x27: ffff80001ec57850
x26: 00000000ffffffff x25: ffff700003d8aec4 x24: ffff0000cfffb200
x23: 0000000000000000 x22: 0000000000000002 x21: ffff0000cb994620
x20: dfff800000000000 x19: 0000000000000000 x18: 0000000000000202
x17: ff80800008335ea8 x16: ffff8000084c316c x15: ffff800008335ea8
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000040000
x11: 000000000000dd81 x10: ffff80001e68a000 x9 : ffff8000108e5500
x8 : 000000000000dd82 x7 : 0000000000000000 x6 : 0000000000000001
x5 : ffff80001ec56858 x4 : 0000000000000100 x3 : ffff8000108e50b4
x2 : ffff0000cb994600 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
fib6_add+0x26fc/0x3400
__ip6_ins_rt net/ipv6/route.c:1302 [inline]
ip6_route_add+0x94/0x17c net/ipv6/route.c:3872
ipv6_route_ioctl+0x3fc/0x670 net/ipv6/route.c:4492
inet6_ioctl+0x2f8/0x380 net/ipv6/af_inet6.c:580
sock_do_ioctl+0x134/0x2dc net/socket.c:1121
sock_ioctl+0x4f0/0x8ac net/socket.c:1238
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 695
hardirqs last enabled at (694): [<ffff800011952c58>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:81 [inline]
hardirqs last enabled at (694): [<ffff800011952c58>] exit_to_kernel_mode+0x100/0x178 arch/arm64/kernel/entry-common.c:91
hardirqs last disabled at (695): [<ffff80001194fe58>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (600): [<ffff8000080300b4>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (680): [<ffff8000108c5920>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (680): [<ffff8000108c5920>] __ip6_ins_rt net/ipv6/route.c:1301 [inline]
softirqs last disabled at (680): [<ffff8000108c5920>] ip6_route_add+0x80/0x17c net/ipv6/route.c:3872
---[ end trace 0a3010e590ca5df0 ]---
---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup