linux-kernel - Re: upstream boot error: can't ssh into the instance (7)

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-prev] [day] [month] [year] [list]

Message-ID: <CACT4Y+bUsYdmAL=dEMv1rA3onETHeZWR4DF1gMzEVbrmFGyrSQ@mail.gmail.com>
Date:   Sat, 22 Feb 2020 08:02:22 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     syzbot <syzbot+b68d37acb74a6ac82cc9@...kaller.appspotmail.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: upstream boot error: can't ssh into the instance (7)

On Sat, Feb 22, 2020 at 6:18 AM syzbot
<syzbot+b68d37acb74a6ac82cc9@...kaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:    11a48a5a Linux 5.6-rc2
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1563eb95e00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=31018567b8f0fc70
> dashboard link: https://syzkaller.appspot.com/bug?extid=b68d37acb74a6ac82cc9
> 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+b68d37acb74a6ac82cc9@...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#status for how to communicate with syzbot.

Somehow "eth0" randomly disappears in some boots...
The same happened before on net and net-next:

Cannot find device "eth0"
Bind socket to interface: No such device
Failed to bring up eth0.