Generalize the inet_diag infrastructure
Status from this message: Applied, with the retention of a NETLINK_INET_DIAG define in patch #1 for
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/11 | inet_diag: Partly rename inet_ to sock_include/ net/ net/ +2 more | +23 | 2 replies | |
| 2/11 | sock_diag: Introduce new message typeinclude/ net/ | +16 | 0 replies | |
| 3/11 | inet_diag: Move byte-code finding up the call-stacknet/ | +17 | 0 replies | |
| 4/11 | inet_diag: Switch from _GETSOCK to IPPROTO_ numbersnet/ net/ net/ | +27 | 0 replies | |
| 5/11 | sock_diag: Initial skeletoninclude/ net/ | +123 | 0 replies | |
| 6/11 | inet_diag: Introduce new inet_diag_req headerinclude/ net/ | +17 | 0 replies | |
| 7/11 | inet_diag: Switch the _get_exact to work with new headernet/ | +22 | 0 replies | |
| 8/11 | inet_diag: Switch the _dump to work with new headernet/ | +53 | 0 replies | |
| 9/11 | inet_diag: Introduce socket family checksnet/ | +11 | 0 replies | |
| 10/11 | inet_diag: Cleanup type2proto last usernet/ | +24 | 0 replies | |
| 11/11 | sock_diag: Move the sock_ code to net/core/net/ net/ net/ | +158 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/11] Generalize the inet_diag infrastructure
This is an attempt to prepare the existing inet_diag infrastructure to work with arbitrary address family and protocol pair, not only AF_INET(6) and TCP/DCCP.
This set adds the sock_diag infrastructure, that handles the new SOCK_DIAG_BY_FAMILY message type by the NETLINK_INET_DIAG socket. The core API struct for this (called sock_diag_req) contains two fields - family and type - which specify which sockets to dump. Additional information is considered to be family handler specific.
The existing inet_diag code is patched to register himself inside the sock_diag and provide callbacks for dumping AF_INET/AF_INET6 IPPROTO_TCP/IPPROTO_DCCP sockets. The existing API facilities such as state filtering and bytecode is of course preserved and is treated by inet_diag specific data.
Binary compatibility with existing NETLINK_INET_DIAG is also kept.
No additional stuff in this set. The support for IPPROTO_UDP protocol and AF_UNIX family will come later if this set is approved.
Applies to net-next, patch for iproute2's ss tool (proving that the new code ... pretends to work) is at the end of the thread.