From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Is it possible to trace events and its call stack?
Date: Thu, 12 Jan 2017 15:46:58 +0530 [thread overview]
Message-ID: <20170112101658.GA3470@naverao1-tp.localdomain> (raw)
In-Reply-To: <b5c14c32-b348-4783-1232-23894080dc5e@cn.fujitsu.com>
On 2017/01/12 03:49PM, Qu Wenruo wrote:
> Hi,
>
> Is it possible to use perf/ftrace to trace events and its call stack?
>
> [Background]
> It's one structure in btrfs, btrfs_bio, I'm tracing for.
> That structure is allocated and free somewhat frequently, and its size is
> not fixed, so no SLAB/SLUB cache is used.
>
> I added trace events(or trace points, anyway, just in
> include/trace/events/btrfs.h) to trace the allocation and freeing.
> Which will output the pointer address of that structure, so I can pair them,
> alone with other info.
>
> Things went well until, I found some structures are allocated but not freed.
> (no corresponding trace point is triggered for given address).
>
> It's possible that btrfs just forget to free it, or btrfs is just holding it
> for some purpose.
> So kernel memleak detector won't catch the later one.
>
> That's to say along with the tracepoint data, I still need the call stack of
> each calling, to determine the code who leak or hold the pointer.
>
> Is it possible to do it using perf or ftrace?
Yes, use -g option with 'perf record'. In fact, I don't think you even
need to add a new tracepoint - you should be able to use kprobes (perf
probe) at structure allocation/free points.
A more efficient way would probably use a eBPF program with stackmaps to
track the stack traces.
- Naveen
next prev parent reply other threads:[~2017-01-12 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 7:49 Is it possible to trace events and its call stack? Qu Wenruo
2017-01-12 10:16 ` Naveen N. Rao [this message]
2017-01-12 20:41 ` Arnaldo Carvalho de Melo
2017-01-16 8:54 ` Qu Wenruo
2017-01-16 2:55 ` Masami Hiramatsu
2017-01-16 8:48 ` Qu Wenruo
2017-01-16 12:26 ` Masami Hiramatsu
2017-01-16 19:32 ` Arnaldo Carvalho de Melo
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=20170112101658.GA3470@naverao1-tp.localdomain \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).