From: Ben Greear <greearb@candelatech.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-kernel@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH 2/2] slub: Add method to verify memory is not deleted.
Date: Mon, 27 Jun 2011 17:24:11 -0700 [thread overview]
Message-ID: <4E091F2B.4060607@candelatech.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106271718340.29910@chino.kir.corp.google.com>
On 06/27/2011 05:19 PM, David Rientjes wrote:
> On Mon, 27 Jun 2011, Ben Greear wrote:
>
>> I saw a case where xprt was 0x6b6b6b6b. I'm trying to figure out
>> what freed it.
>
> And echo 1> /sys/kernel/slab/<cache>/store_user doesn't help?
That gives one method, right? The rpc stuff is freed at the bottom of a
complicated callback chain, and the interesting stuff is what caused the memory
to be freed, not the actually free method.
In previous network (ath9k) hacking I had the same trouble..I think for most
cases you need a full or mostly full stack to make use of the slub
debug logic.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-06-28 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 23:17 [PATCH 0/2] SLUB memory debugging improvements greearb
2011-06-27 23:17 ` [PATCH 1/2] slub: Enable backtrace for create/delete points greearb
2011-06-27 23:17 ` [PATCH 2/2] slub: Add method to verify memory is not deleted greearb
2011-06-27 23:28 ` David Rientjes
2011-06-27 23:46 ` Ben Greear
2011-06-28 0:18 ` Ben Greear
2011-06-28 0:19 ` David Rientjes
2011-06-28 0:24 ` Ben Greear [this message]
2011-06-28 3:45 ` 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=4E091F2B.4060607@candelatech.com \
--to=greearb@candelatech.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.