|| ||Amerigo Wang <firstname.lastname@example.org> |
|| ||email@example.com |
|| ||[Patch v10 0/3] net: reserve ports for applications using fixed port numbers |
|| ||Wed, 5 May 2010 06:26:34 -0400|
|| ||Octavian Purdila <firstname.lastname@example.org>, email@example.com,
Eric Dumazet <firstname.lastname@example.org>,
Neil Horman <email@example.com>,
Amerigo Wang <firstname.lastname@example.org>, email@example.com,
firstname.lastname@example.org, David Miller <email@example.com>|
|| ||Article, Thread
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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/