lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 16 Sep 2010 17:50:39 +0530
From:	Anand Raj Manickam <anandrm@...il.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Eric Dumazet <eric.dumazet@...il.com>, netdev@...r.kernel.org,
	netfilter-devel@...r.kernel.org
Subject: Re: Kernel Panic on OOM with 10 HTB rules

Things seem to be fine now after i reduced imq devs txqueuelen to 32
and MTU to 1600 and no of imqs to 2.
Thank you all for the Suggestions .
Anand

On Thu, Sep 16, 2010 at 3:05 PM, Patrick McHardy <kaber@...sh.net> wrote:
> On 08.09.2010 14:42, Eric Dumazet wrote:
>> Le mercredi 08 septembre 2010 à 16:22 +0530, Anand Raj Manickam a
>> écrit :
>>> I m struck with
>>> Kernel Panic - Out of Memory Issue  when  traffic  is more than 100k
>>> pps  and have  around 10 tc rules.
>>>
>>> There is NO kernel panic with 1 tc rule .
>>>
>>> I using a 2.6.34.6 ( latest stable kernel) with SMP enabled
>>>
>>> The rules are simple -
>>> 10 iptable rules :
>>> iptables -t mangle -I FORWARD -s x.x.x.x  -j CLASSIFY --set-class 0xz:0xy
>>>
>>> 10 tc rules :
>>> tc  class add dev imq0 parent 1:z classid 1:y htb rate 2kbit ceil 32768kbps
>>>
>>> I m using  Intel Xeon Quad core x5570, 12GB RAM , with 8 e1000e , irq
>>> affined ( 1 pair per core)
>>>
>>> There is NO issue / CRASH with multiple iptable rules marking to the
>>> same tc rule/HTB class , i can sucessfully pass more than 200k pps /
>>> 800Mbps traffic .
>>>
>>> But when each iptable rule is marking to seprate tc rule/HTB class and
>>> when the traffic exceeds 100K pps / 20000 connections per second , we
>>> hit this Out of Memory - Kernel panic condition .
>>> Any help is appreciated . Do let me know if any more further
>>> information is need.
>>
>> Hi Anand
>>
>> Could you give :
>>
>> 1) A complete stack trace / panic report
>> 2) cat /proc/interrupts
>> 3) ifconfig -a
>> 4) cat /proc/sys/vm/min_free_kbytes
>> 5) cat /proc/meminfo
>>
>> for each eth*
>>  ethtool -g eth*
>
> Please try to reproduce without the imq patch.
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ