Sysctl namespace support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | sysctl: Add register_sysctl_paths functioninclude/ kernel/ | +84 | 0 replies | |
| 2/4 | sysctl: Remember the ctl_table we passed to register_sysctl_pathsinclude/ kernel/ | +2 | 0 replies | |
| 3/4 | sysctl: Infrastructure for per namespace sysctlsinclude/ kernel/ kernel/ | +111 | 0 replies | |
| 4/4 | net: Implement the per network namespace sysctl infrastructureinclude/ net/ | +66 | 4 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Serge Hallyn |
|---|---|
| 1/4 | |
| 2/4 | |
| 3/4 | |
| 4/4 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] Sysctl namespace support
Currently the network namespace work has gotten about as far as we can without the ability to make sysctls that are per network namespace.
The techniques we have been using for other namespace of examining current and replacing the ctl_table.data field depending on the namespace instance that current->nsproxy refers to are both ugly and do not work for the network sysctls.
The case in handling the networking sysctls that does not work with the existing ugly pointer munging techniques are directories like /proc/sys/net/ipv4/conf/ and /proc/sys/net/ipv4/neigh/ whose contents vary depending on the networking devices present in the network namespace.
Adding support to the sysctl infrastructure to allow to register a sysctl table for a particular instance of a particular namespace removes the need for magic sysctl methods, and allows the use of the techniques for managing dynamic sysctl tables used for years in the network stack.
Herbert we need this infrastructure most in net-2.6.25 (as not having it is a current bottleneck to further development of the network namespace) so these patches are against net-2.6.25.
Andrew also need this infrastructure in -mm so that we can take advantage of this new infrastructure when implementing other namespaces.
So I expect the sane way to deal with this patchset is to merge into both net-2.6.25 and -mm and then Andrew can drop or disable the patches once he pulls bases -mm on a version of net-2.6.25 with the changes.
Eric