DragonFlyBSD Kernel Audit
DF-2631 / env.txt
← back to finding ↓ download raw
# DF-2631 evidence pack environment

Guest: DragonFly dfbsd 6.5-DEVELOPMENT x86_64 (QEMU/KVM, 6 vCPUs, dfbsd-qemu/vm.sh)
  Baseline (stock):  DragonFly dfbsd 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026
                     root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC (INVARIANTS)
  Fix kernels (all "DragonFly dfbsd 6.5-DEVELOPMENT #1", successive
  iterations): 01:26:29 / 01:56:13 / 02:23:41 / 02:52:56 / 03:37:28 /
  04:08:55 / 04:37:14 / 05:10:55 UTC 2026 (Sat Aug 29).  The shipped
  fix.diff corresponds to the 05:10:55 content (final).  Every build:
  cd /usr/src && make nativekernel && make installkernel -> BUILD_RC=0
  (full logs lost to disk reverts between iterations).

hw.ncpu / kern.smp.cpus = 6
vfs.usermount = 0   (root-position; same caveat as DF-2620/DF-2630)
Fix-kernel sysctls: vfs.hammer2.xop_collect_timeout = 60 (validation
  also run at 10), vfs.hammer2.root_timeout = 60

hammer2 thread census on this guest (6 cpus): hammer2_xop_nthreads = 36
groups; 36 h2xop workers per cluster column; 2 sync threads for a
2-master cluster; spmp threads named h2xop-LOCAL / h2nod-LOCAL / etc.

Images (UNMODIFIED — no forged bytes anywhere in this finding):
  base.img  md5 956fc18a70f6689a8669e21d372b4eb9  (newfs_hammer2 -L testvol)
  m1/m2/m3.img = dd/clones of base.img (identical md5) — trigger copies them.