Hello,
syzbot found the following issue on:
HEAD commit: 715abedee4cd Add linux-next specific files for 20230515
git tree: linux-next
console output:
https://syzkaller.appspot.com/x/log.txt?x=15a8c7bd280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=6a2745d066dda0ec
dashboard link:
https://syzkaller.appspot.com/bug?extid=111f4c5258f5ab15ebd7
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/d4d1d06b34b8/disk-715abede.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/3ef33a86fdc8/vmlinux-715abede.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/e0006b413ed1/bzImage-715abede.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+111f4c...@syzkaller.appspotmail.com
sendmmsg$unix(r2, &(0x7f00000002c0), 0x0, 0x8000)
openat$procfs(0xffffffffffffff9c, &(0x7f00000000c0)='/proc/asound/timers\x00', 0x0, 0x0)
unexpected fault address 0x0
fatal error: Connection to 10.128.10.19 closed by remote host.
---
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