panic: 1 -> 0

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: da4a0ea9 Omit files not marked executable from the signatu..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16dd6e3d200000
dashboard link: https://syzkaller.appspot.com/bug?extid=ecec838efb281d6b29c7

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+ecec83...@syzkaller.appspotmail.com

ddb.onpanic: 1 -> 0
Starting network.
IPv6 mode: host
Configuring network interfaces: vioif0vioif0: carrier acquired
DUID 00:01:00:01:23:dd:fc:94:52:54:00:12:34:56
vioif0: IAID 0a:80:00:2b
vioif0: adding address fe80::79db:d97:3808:d899
vioif0: soliciting an IPv6 router
vioif0: soliciting a DHCP lease
vioif0: offered 10.128.0.43 from 169.254.169.254
vioif0: leased 10.128.0.43 for 86400 seconds
vioif0: adding route to 10.128.0.43/32
vioif0: adding host route to 10.128.0.1
vioif0: adding default route via 10.128.0.1
vioif0: Setting hostname: ci2-netbsd-2.c.syzkaller.internal
forked to background, child pid 218
.
Adding interface aliases:.
Waiting for DAD to complete for statically configured addresses...
Starting dhcpcd.
wm0: interface not found or invalid
/etc/rc.d/dhcpcd exited with code 1
Building databases: dev, dev, utmp, utmpx.
wsconscfg: Cannot open `/dev/ttyEcfg': Device not configured
wsconscfg: Cannot open `/dev/ttyEcfg': Device not configured
wsconscfg: Cannot open `/dev/ttyEcfg': Device not configured
wsconscfg: Cannot open `/dev/ttyEcfg': Device not configured
Keyboard wsconsctl: WSKBDIO_SETENCODING: Permission denied
Starting syslogd.
Mounting all file systems...
Clearing temporary files.
Checking quotas: done.
/etc/rc: WARNING: No swap space configured!
/etc/rc.d/swap2 exited with code 1
Starting virecover.
Checking for core dump...
Feb 7 06:28:41 ci2-netbsd-2 savecore: /dev/rsd0b: Device not configured

savecore: /dev/rsd0b: Device not configured
Starting local daemons:.
Updating motd.
Starting powerd.
Starting sshd.


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[Maxime Villard]

#syz invalid