netdev - [syzbot] net-next boot error: can't ssh into the instance (4)

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:   Mon, 17 May 2021 04:18:16 -0700
From:   syzbot <syzbot+f9386e897a8781058604@...kaller.appspotmail.com>
To:     davem@...emloft.net, kuba@...nel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] net-next boot error: can't ssh into the instance (4)

Hello,

syzbot found the following issue on:

HEAD commit:    392c36e5 Merge branch 'ehtool-fec-stats'
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11a7cbf9d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a90b0da0842a411c
dashboard link: https://syzkaller.appspot.com/bug?extid=f9386e897a8781058604

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f9386e897a8781058604@...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.