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]
Message-ID: <000000000000712bf205c28512b3@google.com>
Date:   Mon, 17 May 2021 04:41:19 -0700
From:   syzbot <syzbot+9bc9321e24cb69b1d70b@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
        sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] linux-next boot error: can't ssh into the instance (4)

Hello,

syzbot found the following issue on:

HEAD commit:    18250b53 Add linux-next specific files for 20210416
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15f554c5d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1a0849068413e97e
dashboard link: https://syzkaller.appspot.com/bug?extid=9bc9321e24cb69b1d70b

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ