linux-kernel - [syzbot] riscv/fixes boot error: can't ssh into the instance (2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 01 Jun 2023 09:04:05 -0700
From:   syzbot <syzbot+a74d57bddabbedd75135@...kaller.appspotmail.com>
To:     aou@...s.berkeley.edu, linux-kernel@...r.kernel.org,
        linux-riscv@...ts.infradead.org, palmer@...belt.com,
        paul.walmsley@...ive.com, syzkaller-bugs@...glegroups.com
Subject: [syzbot] riscv/fixes boot error: can't ssh into the instance (2)

Hello,

syzbot found the following issue on:

HEAD commit:    8dc2a7e8027f riscv: Fix relocatable kernels with early alt..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=17e9fbcd280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6b4bf01bbb07f945
dashboard link: https://syzkaller.appspot.com/bug?extid=a74d57bddabbedd75135
compiler:       riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: riscv64

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-8dc2a7e8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/822e3cbe29ad/vmlinux-8dc2a7e8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7bda24abf1c2/Image-8dc2a7e8.xz

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

---
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 syzkaller@...glegroups.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