== DF-0587 PoC run on UNPATCHED baseline kernel ==
    DragonFly 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026

Run command: ./race wlan0   (as unprivileged user maxx)

$ ifconfig wlan0
ifconfig: interface wlan0 does not exist

$ timeout 5 ./race wlan0
DF-0587 race: scan_req vs vap-destroy on wlan0 for 60s...
RUN_EXIT=124

== guest status after run ==
up   (no panic, no crash — bug never reached; no WiFi hardware on guest)

== boot.log tail (serial console — any panic would land here) ==
DragonFly/x86_64 (dfbsd) (ttyd0)
login:

CONCLUSION: PoC cannot trigger the cited race on this guest because the
QEMU/KVM guest has NO IEEE 802.11 radio hardware — there is no wlan(4) vap
and no parent ieee80211com device, so scan_curchan_task is never scheduled.
The wlan stack IS compiled into the default GENERIC kernel (verified:
sys/config/X86_64_GENERIC:255 options IEEE80211_DEBUG; :258 device wlan),
so the vulnerable code is present and would be live on any DragonFly system
with a real wireless adapter — just not exercisable on this VM.

The bug is REAL (code-level trace confirms every hop — see VERDICT.md) but
UNREACHABLE at runtime on this guest. Classification: (d).