/openbmc/linux/net/ipv6/ |
H A D | inet6_hashtables.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/net/ipv4/ |
H A D | inet_hashtables.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | inet_connection_sock.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | sysctl_net_ipv4.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | udp.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | tcp_ipv4.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/include/net/ |
H A D | ip.h | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/drivers/infiniband/core/ |
H A D | cma.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/net/sctp/ |
H A D | socket.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/security/selinux/ |
H A D | hooks.c | 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness
Expansion of original idea from Denis V. Lunev <den@openvz.org>
Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update.
The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net> 227b60f5 Wed Oct 10 19:30:46 CDT 2007 Stephen Hemminger <shemminger@linux-foundation.org> [INET]: local port range robustness Expansion of original idea from Denis V. Lunev <den@openvz.org> Add robustness and locking to the local_port_range sysctl. 1. Enforce that low < high when setting. 2. Use seqlock to ensure atomic update. The locking might seem like overkill, but there are cases where sysadmin might want to change value in the middle of a DoS attack. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
|