From: Liu Bo <bo.li.liu@oracle.com>
To: Zach Brown <zab@zabbo.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Btrfs: add leak debug for extent map
Date: Thu, 10 Jan 2013 10:05:39 +0800 [thread overview]
Message-ID: <20130110020517.GA4456@liubo> (raw)
In-Reply-To: <20130108200734.GD12288@lenny.home.zabbo.net>
On Tue, Jan 08, 2013 at 12:07:34PM -0800, Zach Brown wrote:
> > This is for detecting extent map leak.
>
> Hmm, I guess it's cool to get the allocation-specific decoding which you
> don't get from the generic kernel leak tracking?
Hi Zach,
Thanks for the advice, but what allocation-specific decoding do you refer to?
Could you please show me any examples?
>
> > +static LIST_HEAD(emaps);
>
> > + while (!list_empty(&emaps)) {
> > + em = list_entry(emaps.next, struct extent_map, leak_list);
> > + printk(KERN_ERR "btrfs ext map leak: start %llu len %llu block %llu flags %llu refs %d in tree %d compress %d\n",
> > + em->start, em->len, em->block_start, em->flags, atomic_read(&em->refs), em->in_tree, em->compress_type);
> > + list_del(&em->leak_list);
> > + kmem_cache_free(extent_map_cache, em);
>
> > + struct list_head leak_list;
>
> Might as well protect all that with ifdefs, too, if you're going to do
> it that way?
All right, I'm happy to do that.
Thanks,
liubo
next prev parent reply other threads:[~2013-01-10 2:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 14:49 [PATCH 1/2] Btrfs: add leak debug for extent map Liu Bo
2013-01-08 14:49 ` [PATCH 2/2] Btrfs: fix memory leak on extent map after fsync Liu Bo
2013-01-24 16:44 ` Josef Bacik
2013-01-25 1:38 ` Liu Bo
2013-01-25 2:23 ` Liu Bo
2013-01-24 16:52 ` Josef Bacik
2013-01-08 20:07 ` [PATCH 1/2] Btrfs: add leak debug for extent map Zach Brown
2013-01-10 2:05 ` Liu Bo [this message]
2013-01-10 11:54 ` David Sterba
2013-01-10 13:11 ` Liu Bo
2013-01-11 15:31 ` David Sterba
2013-01-10 17:06 ` Zach Brown
2013-01-11 8:45 ` Liu Bo
2013-01-11 20:54 ` Zach Brown
2013-01-13 12:18 ` Liu Bo
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=20130110020517.GA4456@liubo \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@zabbo.net \
/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).