Repository navigation
docs(specs): say none boxes keep the inet families their netns confines - #1922
Conversation
The NET-137 annotation said only own-address and host-address boxes keep their inet families. A `none` box's fresh network namespace confines them too, holding only loopback, so it keeps them as well.
|
Warning Review limit reached
This review includes 1 billable file and costs up to $0.25.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 40 minutes for your next included review. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
Comment |
Spec lint
Advisory. None of this blocks the merge; the review decides. Advisory, and never a merge gate. Linter: |
|
Approved: no findings at Nothing to do. Clobber: none: |
Rewords the NET-137 annotation in spec 18. It said only own-address and host-address boxes keep their inet families, which reads as excluding `none` boxes. A `none` box's fresh network namespace confines AF_INET/AF_INET6/AF_NETLINK (it holds only loopback), so it keeps them too. The EARS requirement text is unchanged.
Motivated by #1883, which admits those families in the
noneseal when the box has its own namespace.just lint-prosereports no alerts on the touched line; the file's totals match main.