From: PuiFunLau@cs.com
To: linux-kernel@vger.kernel.org
Subject: kernel oops during kfree_skbmem
Date: Thu, 29 Mar 2001 00:10:25 EST [thread overview]
Message-ID: <d5.454c391.27f41dc1@cs.com> (raw)
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 <free_block+84/d8> <=====
Trace; c011b77a <do_softirq+5a/88>
Trace; c012c82a <kfree+72/98>
Trace; c01d00fd <kfree_skbmem+25/80>
Trace; c01d024b <__kfree_skb+f3/f8>
Trace; c01d0d1d <skb_free_datagram+1d/24>
Trace; c0203a61 <packet_recvmsg+139/148>
Trace; c01cd441 <sock_recvmsg+41/b0>
Trace; c0203928 <packet_recvmsg+0/148>
Trace; c01ce2fd <sys_recvfrom+ad/108>
Allen Lau
reply other threads:[~2001-03-29 5:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5.454c391.27f41dc1@cs.com \
--to=puifunlau@cs.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox