linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: ziegler@uni-freiburg.de
Cc: Josef Bacik <jbacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kmem_cache_destroy called for cache that still has objects
Date: Wed, 04 Jul 2012 15:53:34 +0200	[thread overview]
Message-ID: <4FF44ADE.8000207@jan-o-sch.net> (raw)
In-Reply-To: <4FF1C140.3070705@jan-o-sch.net>

Hi Martin,

On 02.07.2012 17:41, Jan Schmidt wrote:
> I'm recently seeing such buffer leaks as well. It's always about tree blocks,
> and it's always just two or three refs left for a buffer. I can somehow
> reproduce it and will be looking into it probably tomorrow. (May still be
> unrelated, of course.)

Okay, I've tracked my buffer leak down. It's most likely unrelated to yours, as
you need Chris' current for-linus for that to occur. Second, you need to trigger
a lot of tree mod log operations (i.e. by calling "btrfs inspect-internal" while
modifying the trees).

I'm sending a fix for the problem I found. However, there's no obvious
reproducer for your problem yet. Can you reproduce it?

-Jan

  reply	other threads:[~2012-07-04 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 13:52 kmem_cache_destroy called for cache that still has objects Martin Ziegler
2012-07-02 15:41 ` Jan Schmidt
2012-07-04 13:53   ` Jan Schmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-02 11:06 Martin Ziegler
2012-07-02 12:48 ` Josef Bacik

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=4FF44ADE.8000207@jan-o-sch.net \
    --to=list.btrfs@jan-o-sch.net \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ziegler@uni-freiburg.de \
    /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).