From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Subject: Use-after-free in pte_chain in 2.6.0-test11
Date: Sat, 13 Dec 2003 23:04:59 +0100 [thread overview]
Message-ID: <20031213220459.GA22152@vana.vc.cvut.cz> (raw)
Hi,
today I get this one while attempting to build new kernel. Running kernel is
2.6.0-test11-c1511 (bk as of 2003-12-05 23:35:35-08:00). Does anybody
have any clue what could happen, or should I start looking for a new
memory modules?
AMD K7/1GHz box, 512MB RAM, no vmmon/vmnet loaded since reboot, gcc-3.3.2
as of last week Debian unstable. Kernel built with all possible memory
debugging enabled...
Unfortunately I have no idea which process did this clone() call, and
whether it succeeded or died.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
Slab corruption: start=da54d380, expend=da54d3ff, problemat=da54d3fc
Data: ****************************************************************************************************************************6A **A5
Next: 1D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
slab error in check_poison_obj(): cache `pte_chain': object was modified after freeing
Call Trace:
[<c0152658>] check_poison_obj+0x108/0x190
[<c0166e3c>] pte_chain_alloc+0x3c/0x80
[<c0154813>] kmem_cache_alloc+0x83/0x210
[<c0166e3c>] pte_chain_alloc+0x3c/0x80
[<c015d1b0>] copy_page_range+0x410/0x900
[<c0152579>] check_poison_obj+0x29/0x190
[<c0125c51>] copy_mm+0x571/0x730
[<c0127369>] copy_process+0xcd9/0xee0
[<c0126bc2>] copy_process+0x532/0xee0
[<c01275cc>] do_fork+0x5c/0x1e0
[<c01078d1>] sys_clone+0x41/0x50
[<c0109dab>] syscall_call+0x7/0xb
next reply other threads:[~2003-12-13 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 22:04 Petr Vandrovec [this message]
2003-12-13 22:13 ` William Lee Irwin III
2003-12-13 22:32 ` Petr Vandrovec
2003-12-13 22:33 ` William Lee Irwin III
2003-12-13 22:36 Manfred Spraul
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=20031213220459.GA22152@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--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
all inboxes | Powered by JetHome®