aboutsummaryrefslogtreecommitdiffstats
path: root/include/pcmcia
diff options
context:
space:
mode:
authorHannes Frederic Sowa <hannes@stressinduktion.org>2013-03-15 11:32:30 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-03-28 12:05:59 -0700
commit7b7a1b8b3bd1742ca5ab259e741da0070e936db0 (patch)
treeea200e510b59ba89bea5fd56a071e4f0d2d92f50 /include/pcmcia
parent110789df9f88361dcf6b5dad53a38ea2f88cad77 (diff)
downloadkernel_samsung_smdk4412-7b7a1b8b3bd1742ca5ab259e741da0070e936db0.zip
kernel_samsung_smdk4412-7b7a1b8b3bd1742ca5ab259e741da0070e936db0.tar.gz
kernel_samsung_smdk4412-7b7a1b8b3bd1742ca5ab259e741da0070e936db0.tar.bz2
inet: limit length of fragment queue hash table bucket lists
[ Upstream commit 5a3da1fe9561828d0ca7eca664b16ec2b9bf0055 ] This patch introduces a constant limit of the fragment queue hash table bucket list lengths. Currently the limit 128 is choosen somewhat arbitrary and just ensures that we can fill up the fragment cache with empty packets up to the default ip_frag_high_thresh limits. It should just protect from list iteration eating considerable amounts of cpu. If we reach the maximum length in one hash bucket a warning is printed. This is implemented on the caller side of inet_frag_find to distinguish between the different users of inet_fragment.c. I dropped the out of memory warning in the ipv4 fragment lookup path, because we already get a warning by the slab allocator. Cc: Eric Dumazet <eric.dumazet@gmail.com> Cc: Jesper Dangaard Brouer <jbrouer@redhat.com> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Acked-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/pcmcia')
0 files changed, 0 insertions, 0 deletions