⬢ DragonFlyBSD Kernel Audit
DF-2305 / run.log
← back to finding ↓ download raw
=== DF-2305 baseline: leaked error path vs sibling cleanup ===
--- A: dmatag-fail at fwohci_pci.c:320
ATTACH: attach rc=12 mode=0x2
ATTACH: resource deltas: MEM 1/0  IRQ 1/0  setup_intr 1 teardown 0 live_handlers=1
ATTACH: interposers: dpa_calls=0 dmatag_calls=1 mem_conflict_fails=0
ATTACH: device_delete_child calls: 0
--- C: rig-only forced detach (stock never does this here)
FORCEDETACH: rc=0
STATS: MEM 1/1 IRQ 1/1 setup 1 teardown 1 live=0 conflicts=0 deletes=0
--- D: sibling path irq-alloc-fail (fwohci_pci.c:280) -> detach
ATTACH: attach rc=6 mode=0x4
ATTACH: resource deltas: MEM 1/1  IRQ 0/0  setup_intr 0 teardown 0 live_handlers=0
ATTACH: interposers: dpa_calls=0 dmatag_calls=0 mem_conflict_fails=0
ATTACH: device_delete_child calls: 0
STATS: MEM 2/2 IRQ 1/1 setup 1 teardown 1 live=0 conflicts=0 deletes=0
--- B: re-attach on the still-leaked BAR (expect conflict)
ATTACH: attach rc=12 mode=0x2
ATTACH: resource deltas: MEM 1/0  IRQ 1/0  setup_intr 1 teardown 0 live_handlers=1
ATTACH: interposers: dpa_calls=0 dmatag_calls=1 mem_conflict_fails=0
ATTACH: device_delete_child calls: 0
ATTACH: attach rc=6 mode=0x0
ATTACH: resource deltas: MEM 0/0  IRQ 0/0  setup_intr 0 teardown 0 live_handlers=1
ATTACH: interposers: dpa_calls=0 dmatag_calls=0 mem_conflict_fails=1
ATTACH: device_delete_child calls: 0
=== DF-2305 baseline done ===