From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Question on debugging use-after-free memory issues.
Date: Mon, 27 Jun 2011 11:12:27 -0700 [thread overview]
Message-ID: <4E08C80B.9070602@candelatech.com> (raw)
I have a case where deleted memory is being passed into an RPC
callback. I enabled SLUB memory poisoning and verified that the
data pointed to has 0x6b...6b value.
Unfortunately, the rpc code is a giant maze of callbacks and I'm
having a difficult time figuring out where this data could be erroneously
deleted at.
So first question:
Given a pointer to memory, and with SLUB memory debuging on (and/or other
debugging options if applicable), is there a way to get any info about where
the memory was last deleted?
Second: Any other suggestions for how to go about debugging this?
I hit this problem under load after multiple hours, so just adding printks
in random places may not be feasible...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2011-06-27 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 18:12 Ben Greear [this message]
2011-06-28 22:00 ` Question on debugging use-after-free memory issues Jiri Kosina
2011-06-29 5:41 ` Eric Dumazet
2011-06-29 6:01 ` Ben Greear
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=4E08C80B.9070602@candelatech.com \
--to=greearb@candelatech.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