| To: | Imran.Patel@xxxxxxxxx |
|---|---|
| Subject: | Re: skb allocation problems (More Brain damage!) |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Wed, 11 Apr 2001 20:28:31 +0200 |
| Cc: | ak@xxxxxxx, netfilter-devel@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <2D6CADE9B0C6D411A27500508BB3CBD063CF2D@eseis15nok>; from Imran.Patel@xxxxxxxxx on Wed, Apr 11, 2001 at 08:15:49PM +0300 |
| References: | <2D6CADE9B0C6D411A27500508BB3CBD063CF2D@eseis15nok> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Wed, Apr 11, 2001 at 08:15:49PM +0300, Imran.Patel@xxxxxxxxx wrote: > And as a I said earlier, only ping packets with size within certain range > create this problem......Something is terribly wrong here!! But as I am not > a Linux mm guru, i can't tell what is wrong here! What you can try is to turn on slab debugging. Set the FORCED_DEBUG define in mm/slab.c to one and recompile. Does it change any pattern when you dump the data in the skbs or pings? If yes someone is playing with already freed packets. Furthermore you can instrument other parts with good old printk. And what NIC are you using btw? -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: skb allocation problems (More Brain damage!), Andi Kleen |
|---|---|
| Next by Date: | RE: skb allocation problems (More Brain damage!), Imran . Patel |
| Previous by Thread: | Re: skb allocation problems (More Brain damage!), Andi Kleen |
| Next by Thread: | RE: skb allocation problems (More Brain damage!), Imran . Patel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |