oops during kfree_skbmem
I am reposting... the oops call stack didn't show up correctly. >>EIP; c012c504<= Trace; c011b77a Trace; c012c82a Trace; c01d00fd Trace; c01d024b <__kfree_skb+f3/f8> Trace; c01d0d1d Trace; c0203a61 Trace; c01cd441 Trace; c0203928 Trace; c01ce2fd The oops happened on a box running Linux 2.4.0 and libpcap-0.6.2 (which uses AF_PACKET socket). The packet received was an arp request. I have syslog indicating the kernel received the arp request. My pcap application captures arp packet as well. The calls leading to the oops : pcap_dispatch ... sys_recvfrom ... kfree_skbmem ...free_block. The oops is not recreatable on demand. However, on another box running 2.4.0-test7, there is a memory leak. Top reports memory used by my application stable at 0.3%, but system memory usage keeps going up (reaching 250M used, 4M free before staying there). Allen Lau - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
kernel oops during kfree_skbmem
I posted the following to tcpdump-workers. They think I should ask here... I was almost certain the following kernel oops occurred during packet capture. The packet received was an arp request. Syslog indicated the kernel received the arp request. My pcap application captures arp packet as well. The calls leading to the oops : pcap_dispatch ... sys_recvfrom ... kfree_skbmem ...free_block. The oops happened on a box running Linux 2.4.0 and libpcap-0.6.2 (which uses AF_PACKET socket). The decoded call stack of the oops is below. The oops does not happen all the time. However, on another box running 2.4.0-test7 and the same application, there is a memory leak. TOP reports memory used by my application stable at 0.3%, but system memory usage keeps going up (reaching 250M used, 4M free before staying there). Does this look like a libpcap problem or skbmem problem? Are there two copies of the same packet when I do packet capture? >>EIP; c012c504<= Trace; c011b77a Trace; c012c82a Trace; c01d00fd Trace; c01d024b <__kfree_skb+f3/f8> Trace; c01d0d1d Trace; c0203a61 Trace; c01cd441 Trace; c0203928 Trace; c01ce2fd Allen Lau - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
