net: reserve ports for applications using fixed port numbers
Status from this message: Applied to net-next-2.6, thanks.
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v10 Latest3 patches 2 repliesApplied
- v93 patches 5 repliesSuperseded
- v83 patches 8 repliesSuperseded
Earlier versions · 3
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v7 | 3 patches | 9 replies | Superseded | |
| v2 RFC | 1 patch | 4 replies | Superseded | |
| v1 RFC | 1 patch | 21 replies | Superseded |
Changes from the previous version from the cover letter
- Use 'true' and 'false' for bool's;
- Fix some coding style problems;
- Allow appending lines to bitmap proc file so that it will be easier to add new bits.
Patches in v10 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | sysctl: refactor integer handling proc codekernel/ | +229 | 0 replies | |
| 2/3 | sysctl: add proc_do_large_bitmapinclude/ kernel/ | +163 | 0 replies | |
| 3/3 | net: reserve ports for applications using fixed port numbersDocumentation/ include/ net/ +5 more | +73 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v10 yet.
Cover letter [Patch v10 0/3] net: reserve ports for applications using fixed port numbers
Changes from the previous version:
- Use 'true' and 'false' for bool's;
- Fix some coding style problems;
- Allow appending lines to bitmap proc file so that it will be easier to add new bits.
------------------>
This patch introduces /proc/sys/net/ipv4/ip_local_reserved_ports which allows users to reserve ports for third-party applications.
The reserved ports will not be used by automatic port assignments (e.g. when calling connect() or bind() with port number 0). Explicit port allocation behavior is unchanged.
There are still some miss behaviors with regard to proc parsing in odd invalid cases (for "40000\0-40001" all is acknowledged but only 40000 is accepted) but they are not easy to fix without changing the current "acknowledge how much we accepted" behavior.
Because of that and because the same issues are present in the existing proc_dointvec code as well I don't think its worth holding the actual feature (port reservation) after such petty error recovery issues.