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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:   Tue, 18 Dec 2018 05:41:03 -0800
From:   syzbot <syzbot+ea0064d0f1f70a0a596d@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: linux-next boot error: can't ssh into the instance: failed to run
 ["ssh" "-p" "22" "-i" "/syzkaller/managers/upstream-linux-next-kasan-gce-root/latest.tmp/key"
 "-F" "/dev/null" "-o" "UserKnownHostsFil

Hello,

syzbot found the following crash on:

HEAD commit:    285053b5a4c0 Add linux-next specific files for 20181218
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16572b2b400000
kernel config:  https://syzkaller.appspot.com/x/.config?x=93f80ae0acf2571f
dashboard link: https://syzkaller.appspot.com/bug?extid=ea0064d0f1f70a0a596d
compiler:       gcc (GCC) 8.0.1 20180413 (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+ea0064d0f1f70a0a596d@...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