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: <000000000000dc52b305810d0f49@google.com>
Date:   Mon, 04 Feb 2019 00:13:04 -0800
From:   syzbot <syzbot+94522064b07f06df116d@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: linux-next boot error: can't ssh into the instance (2)

Hello,

syzbot found the following crash on:

HEAD commit:    66d54fa79f95 Add linux-next specific files for 20190204
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17823b28c00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f0f6544db42451b4
dashboard link: https://syzkaller.appspot.com/bug?extid=94522064b07f06df116d
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

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



---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with  
syzbot.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ