]> bbs.cooldavid.org Git - net-next-2.6.git/commit - net/ipv4/inet_connection_sock.c
[INET]: Justification for local port range robustness.
authorAnton Arapov <aarapov@redhat.com>
Fri, 19 Oct 2007 05:00:17 +0000 (22:00 -0700)
committerDavid S. Miller <davem@davemloft.net>
Fri, 19 Oct 2007 05:00:17 +0000 (22:00 -0700)
commita25de534f89c515c82d3553c42d3bb02c2d1a7da
treed09a5ed1f8a9fa5254c9ebf5cb49bf95e636a3e8
parentbe702d5e38e2e7e554604b223794f87c12fa6811
[INET]: Justification for local port range robustness.

  There is a justifying patch for Stephen's patches. Stephen's patches
disallows using a port range of one single port and brakes the meaning
of the 'remaining' variable, in some places it has different meaning.
My patch gives back the sense of 'remaining' variable. It should mean
how many ports are remaining and nothing else. Also my patch allows
using a single port.

  I sure we must be able to use mentioned port range, this does not
restricted by documentation and does not brake current behavior.

usefull links:
Patches posted by Stephen Hemminger
  http://marc.info/?l=linux-netdev&m=119206106218187&w=2
  http://marc.info/?l=linux-netdev&m=119206109918235&w=2

Andrew Morton's comment
  http://marc.info/?l=linux-kernel&m=119248225007737&w=2

1. Allows using a port range of one single port.
2. Gives back sense of 'remaining' variable.

Signed-off-by: Anton Arapov <aarapov@redhat.com>
Acked-by: Stephen Hemminger <shemminger@linux-foundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/infiniband/core/cma.c
net/ipv4/inet_connection_sock.c
net/ipv4/inet_hashtables.c
net/ipv4/sysctl_net_ipv4.c
net/ipv4/udp.c
net/ipv6/inet6_hashtables.c