[syzbot] linux-next boot error: general protection fault in corrupted

5 views
Skip to first unread message

syzbot

unread,
Mar 27, 2023, 2:03:59 PM3/27/23
to linux-...@vger.kernel.org, linux...@vger.kernel.org, s...@canb.auug.org.au, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7c4a254d78f8 Add linux-next specific files for 20230323
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14001a7ac80000
kernel config: https://syzkaller.appspot.com/x/.config?x=20fd034702e6edd2
dashboard link: https://syzkaller.appspot.com/bug?extid=8fddae658688311a9edc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dc0bbbecd2a5/disk-7c4a254d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6b2c8c7cfd4b/vmlinux-7c4a254d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ae312a388585/bzImage-7c4a254d.xz

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

mount: mounting selinuxfs on /sys/fs/selinux failed: No such file or directory
mount: mounting mqueue on /dev/mqueue failed: No such file or di[ 19.342818][ T4416] mount (4416) used greatest stack depth: 23336 bytes left
rectory
mount: mounting hugetlbfs on /dev/hugepages failed: No such file or directory
mount: mounting fuse.lxcfs on /var/lib/lxcfs failed: No such file or directory
Starting syslogd: [ 19.633755][ T4426] general protection fault, probably for non-canonical address 0xdffffc000000005d: 0000 [#1] PREEMPT SMP KASAN


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

syzbot

unread,
May 22, 2023, 1:59:45 PM5/22/23
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages