⬢ DragonFlyBSD Kernel Audit
DF-2799 / run.log
← back to finding ↓ download raw 
+ V=dfbsd-qemu/vm.sh
+ D=/tmp/df2799
+ dfbsd-qemu/vm.sh run_root 'cd /tmp/df2799 && timeout 10 ./listonce; echo PRE-LISTONCE-RC:$?; timeout 10 ./jailonce; echo PRE-JAILONCE-RC:$?'
timeout: exec(./listonce): No such file or directory
PRE-LISTONCE-RC:127
timeout: exec(./jailonce): No such file or directory
PRE-JAILONCE-RC:127
+ dfbsd-qemu/vm.sh run_user 'cd /tmp/df2799 && nohup ./jailistreader 0 > /tmp/reader1.log 2>&1 & nohup ./jailistreader 0 > /tmp/reader2.log 2>&1 & nohup ./jailistreader 0 > /tmp/reader3.log 2>&1 & nohup ./jailistreader 0 > /tmp/reader4.log 2>&1 & sleep 1; echo READERS-STARTED'
READERS-STARTED
+ dfbsd-qemu/vm.sh run_root 'cd /tmp/df2799 && nohup ./jailchurn 200000 > /tmp/churn.log 2>&1 & sleep 2; echo CHURN-STARTED'
CHURN-STARTED
+ sleep 10
+ dfbsd-qemu/vm.sh run_root 'cd /tmp/df2799 && timeout 15 ./listonce; echo LISTONCE-RC:$?'
timeout: exec(./listonce): No such file or directory
LISTONCE-RC:127
+ dfbsd-qemu/vm.sh run_root 'cd /tmp/df2799 && timeout 15 ./jailonce; echo JAILONCE-RC:$?'
timeout: exec(./jailonce): No such file or directory
JAILONCE-RC:127
+ dfbsd-qemu/vm.sh run_root 'echo STILL-ALIVE; date; ps ax | grep -E "jailchurn|jailistreader" | grep -v grep | head -14'
STILL-ALIVE
Tue Sep  1 12:51:49 UTC 2026
  1148 ??  R3       0:09.49 ./jailistreader 0
  1159 ??  D5       0:07.13 ./jailchurn 200000
 28190 ??  ZJy      0:00.00 (jailchurn)
 28191 ??  ZJy      0:00.00 (jailchurn)
 28192 ??  ZJy      0:00.00 (jailchurn)
 28194 ??  ZJy      0:00.00 (jailchurn)
 28195 ??  ZJy      0:00.00 (jailchurn)
 28196 ??  ZJy      0:00.01 (jailchurn)
 28197 ??  ZJy      0:00.00 (jailchurn)
 28198 ??  ZJy      0:00.00 (jailchurn)
 28199 ??  ZJy      0:00.00 (jailchurn)
 28200 ??  ZJy      0:00.00 (jailchurn)
 28201 ??  ZJy      0:00.03 (jailchurn)
 28202 ??  ZJy      0:00.00 (jailchurn)
+ dfbsd-qemu/vm.sh log 40
hammer2_mount: hmp=0xfffff8008fae0000 pmp=0xfffff80090280000
DMA space used: 13580k, remaining available: 131072k
Mounting devfs
Loading configuration files.
Loading devfs rules: /etc/defaults/devfs.conf.
Initializing random seed: done. 
dumpon: crash dumps to /dev/vbd0s1b (25, 0x20001)
Starting file system checks:
/dev/vbd0s1a: 713 files, 408700 used, 114459 free (163 frags, 14287 blocks, 0.0% fragmentation)
mount_hammer2: unable to connect to cluster controller
mount_hammer2: cluster_connect(/dev/vbd0s1d@ROOT) failed
hammer2_mount: "vbd0s1d": no recovery needed
hammer2: enable read/write
HAMMER2: VOLDATA DUMP
HAMMER2: INITIATE SPANs
mount_hammer2: unable to connect to cluster controller
mount_hammer2: cluster_connect(/dev/vbd0s1d@ROOT) failed
Mounting tmpfs at /var/run/shm.
Setting hostname: dfbsd.
Starting dhclient.
starting dhclient on vtnet0
lo0: flags=808049<UP,LOOPBACK,RUNNING,MULTICAST,PROXY> metric 0 mtu 16384
	options=43<RXCSUM,TXCSUM,RSS>
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
	groups: lo
vtnet0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,PROXY> metric 0 mtu 1500
	options=28<VLAN_MTU,JUMBO_MTU>
	ether 52:54:00:12:34:56
	inet6 fe80::5054:ff:fe12:3456%vtnet0 prefixlen 64 tentative scopeid 0x1
	media: Ethernet 1000baseT <full-duplex>
	status: active
add net default: gateway 10.0.2.2
Additional routing options:.
Starting devd.
Additional TCP options:.
Mounting NFS file systems:.
ELF ldconfig path: /lib /usr/lib /usr/local/lib /usr/local/libdata/ldconfig/pkg
Building databases...
Starting syslogd.
Sep  1 12:23:49 dfbsd syslogd: kernel boot file is /boot/kernel/kernel

No core dumps found.
swap low/high-water marks set to 41940/62910
swapon: adding /dev/vbd0s1b as swap device
NFS CLIENT: access_cache_timeout=5 neg_cache_timeout=3.
Starting local daemons:.
Updating motd.
Configuring syscons: blanktime.
Starting sshd.
sendmail_submit: /etc/mail/aliases.db not present,  generating
sendmail_clientmqueue: /etc/mail/aliases.db not present,  generating
Starting cron.
Local package initialization:.

Tue Sep  1 12:23:49 UTC 2026


DragonFly/x86_64 (dfbsd) (ttyd0)



login: maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
maxproc limit of 1970 exceeded by "jailchurn" uid 0, please see tuning(7) and login.conf(5).
=== evidence: post-storm probes ===
POST-STORM PROBES (fresh guest, 4 readers on jail.list + churn 3000):
  - launch cmd (nohup churn + sleep 2 + pgrep) never returned (120s host timeout)
  - PROBE1: timeout 30 ssh 'timeout 10 ./listonce; echo LISTONCE-RC:$?' -> NO OUTPUT (124)
  - TRIVIAL: timeout 25 ssh 'echo TRIVIAL-ALIVE; date' -> NO OUTPUT (124)  [even exec of /bin/echo wedges: rtld sysctls block on exclusively-held per-CPU gd_sysctllock]
  - MARKERS: timeout 40 ssh '(timeout 10 ./listonce; ... ) > /tmp/markers.out; cat' -> NO OUTPUT (124)
  - serial console: 'maxproc limit of 1970 exceeded by "jailchurn" uid 0' flood
    (parent churner deadlocked mid-jail(2) forever, never reaps -> children hit maxproc)
  - flood lines in serial log: 0  (NO id-reuse/truncation sharing at 3000 iterations ->
     this wedge is PURELY the jail_lock <-> gd_sysctllock AB-BA cycle)
  - pre-storm controls on same guest: PRE-LISTONCE:0 (listonce ok, 0 bytes), PRE-JAILONCE:0