From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 497] New: conntrack related slab corruption.
Date: Mon, 24 Mar 2003 14:20:15 -0800 [thread overview]
Message-ID: <558030000.1048544415@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=497
Summary: conntrack related slab corruption.
Kernel Version: 2.5.65
Status: NEW
Severity: normal
Owner: laforge@gnumonks.org
Submitter: davej@codemonkey.org.uk
Slab corruption: start=cf480a84, expend=cf480bb7, problemat=cf480aec
Last user: [<c03ed43a>](destroy_conntrack+0xf8/0x159)
Data:
+****************************************************************************************+****************EC
0A 48 CF EC 0A 48 CF
+****************************************************************************************+****************************************************************************************+*******************A5
Next: 71 F0 2C .3A D4 3E C0 71 F0 2C .********************
slab error in check_poison_obj(): cache `ip_conntrack': object was modified
after freeingCall Trace:
[<c0144496>] check_poison_obj+0x155/0x195
[<c0145e4b>] kmem_cache_alloc+0x139/0x177
[<c03edfba>] init_conntrack+0x8d/0x44f
[<c03edfba>] init_conntrack+0x8d/0x44f
[<c03ee586>] ip_conntrack_in+0x20a/0x2bc
[<c03db2eb>] udp_connect+0xa8/0x353
[<c03aa074>] nf_iterate+0x5f/0x93
[<c03b9634>] dst_output+0x0/0x2d
[<c03aa3db>] nf_hook_slow+0xa9/0x205
[<c03b9634>] dst_output+0x0/0x2d
[<c03b7a84>] ip_queue_xmit+0x435/0x525
[<c03b9634>] dst_output+0x0/0x2d
[<c039d1df>] __kfree_skb+0x89/0xfe
[<c014437c>] check_poison_obj+0x3b/0x195
[<c03d0eeb>] tcp_v4_send_check+0x4d/0xd8
[<c03ca6ae>] tcp_transmit_skb+0x3b0/0x5b3
[<c03cd026>] tcp_connect+0x3af/0x47b
[<c02aa34e>] secure_tcp_sequence_number+0x82/0xa0
[<c03d0237>] tcp_v4_connect+0x393/0x5db
[<c03e3f1d>] inet_stream_connect+0x264/0x3bc
[<c0398ae2>] move_addr_to_kernel+0x6b/0x6f
[<c039a2d8>] sys_connect+0x78/0x99
[<c0398c00>] sock_destroy_inode+0x1d/0x21
[<c0398c00>] sock_destroy_inode+0x1d/0x21
[<c0178bbc>] destroy_inode+0x36/0x50
[<c017a493>] iput+0x63/0x7c
[<c01760b3>] dput+0x24/0x333
[<c039adb1>] sys_socketcall+0xb2/0x262
[<c015c938>] filp_close+0xe9/0x12d
[<c015ca13>] sys_close+0x97/0xdf
[<c010978f>] syscall_call+0x7/0xb
reply other threads:[~2003-03-24 22:19 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=558030000.1048544415@flay \
--to=mbligh@aracnet.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