⬢ DragonFlyBSD Kernel Audit
DF-2433 / run.log
← back to finding ↓ download raw
===DF-2434 loop attempts (production ccdioctl SET/CLR via rig)===
dfmisc: ccd loop ileave=32 cycles=3000 ok=0 setfail=3000 clrfail=0
dfmisc: ccd loop ileave=0  cycles=3000 ok=0 setfail=3000 clrfail=0
dfmisc: first SET failed: 16 (EBUSY)

Environment blocker, observed repeatedly this session: after the FIRST
successful CCDIOCSET on a unit (verified earlier: SET_rc=0, /dev/ccd0s0
auto-created by the MBR probe), the auto-created compat slice pins a
reference on cs->sc_dev so every subsequent CCDIOCCLR returns EBUSY
("ccd0: In use, cannot detach" at kldunload too), and the component
devices stay v_opencount-pinned (vn2s0a/vn3s0a permanently busy) --
the leaked-config pinning the DF-2433 race predicts, observed live.
With SET/CLR cycling unavailable, the per-cycle ii_index leak
(DF-2434: kmalloc at ccd.c:670 before the smallci test; terminator
never freed by the ccd.c:1460 loop) cannot be accumulated on this
snapshot.  Code defect line-accurate; mechanical demo env-blocked.