# Guest environment + fix compile-validation session — 2026-09-23 (audit guest)

uname -a:
DragonFly dfbsd 6.5-DEVELOPMENT DragonFly 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026     root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC  x86_64
cc: 8.3 [DragonFly] Release/2019-02-22

Guest /usr/src/sys/dev/netif/ig_hal/e1000_vf.c:
  SHA256 = c0cdce6b90e860665142e690ee34ffbf0f70332a2c6cb45a3719a4c217d19dd2
  (bit-identical to the audited tree file)

pciconf -l | grep -iE "igb|em[0-9]|82576|intel" -> NO_E1000_HW
ifconfig -l                                     -> vtnet0 lo0   [virtio-only]

=> no SR-IOV 82576/I350 VF device on this guest: the mailbox data path of
   e1000_update_mc_addr_list_vf() cannot be exercised at runtime here;
   PoC status untested / attempts 0. The logic-level behavior is proven
   from source ordering + upstream divergence (VERDICT.md, run.log).

Fix compile validation (exact hunks of fix.diff applied to a copy of the
pristine file with patch(1) on the guest):

  baseline:  cc -fsyntax-only -D_KERNEL -I/usr/obj/usr/src/sys/X86_64_GENERIC \
             -I/usr/src/sys -I/usr/src/sys/dev/netif/ig_hal e1000_vf_base.c \
             -> BASE_CC_RC=0
  patched:   same flags on e1000_vf.c (sha256 c3997db5a0…) -> FIXED_CC_RC=0
  (only pre-existing warning: systm.h:216 'log' builtin-declaration-mismatch)

Guest left clean (/tmp/vfchk removed; guest_dirty=0).