⬢ DragonFlyBSD Kernel Audit
DF-3534 / isolation.log
← back to finding ↓ download raw
# DF-3534 isolation runs (kernel #1 + layer-2 module, BEFORE the ngt_shutdown
# NG_NODE_UNREF fix; vmstat -m | grep netgraph_node):
--- nodd (TIOCSETD on/off only: no hook, no data, no timer) ---
      netgraph_node       3     400
done nodd 500
      netgraph_node     503    86.5K        <-- +1 node/cycle
--- nodata (connect a socket hook, no data) ---
done nodata 500
      netgraph_node    1003    173K         <-- +1 node/cycle
--- socksock (socket<->socket connect+data, no tty at all) ---
done socksock 500
      netgraph_node    1003    173K         <-- FLAT (generic path clean)
--- full (tty connect+data) ---
done full 500
      netgraph_node   1.47K    275K         <-- +1 node/cycle (same rate as nodd)
#
# => the node leak is pure ng_tty ldisc open/close, independent of hooks,
#    data, or the chand callout (DF-3531), and independent of the generic
#    ng7 connect/data machinery.
#
# AFTER the fix (NG_NODE_UNREF added to ngt_shutdown, fix_validation.log):
#   nodd 500:                    nodes 2 -> 2 (FLAT)
#   stall-close 2000 + 2000:     nodes 2 -> 2 -> 2 (FLAT), hooks 0 in-use