From: Mike Snitzer <snitzer@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: dm-devel@redhat.com, xfs@oss.sgi.com
Subject: Re: xfs_btree_cur leak with 3.5-rc4
Date: Mon, 2 Jul 2012 21:26:28 -0400 [thread overview]
Message-ID: <20120703012628.GA5710@redhat.com> (raw)
In-Reply-To: <20120703002611.GW19223@dastard>
On Mon, Jul 02 2012 at 8:26pm -0400,
Dave Chinner <david@fromorbit.com> wrote:
> On Mon, Jul 02, 2012 at 03:14:12PM -0400, Mike Snitzer wrote:
> > I get kmemleak reports against XFS when I run the thinp-test-suite
> > against 3.5-rc4. I didn't see any XFS leaks with 3.4.
>
> Already fixed in 3.5-rc5:
>
> 76d0953 xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near
Odd, I already have that fix (as it was included in 3.5-rc4).
I'll double check though I see the leak though.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-03 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 19:14 xfs_btree_cur leak with 3.5-rc4 Mike Snitzer
2012-07-03 0:26 ` Dave Chinner
2012-07-03 1:26 ` Mike Snitzer [this message]
2012-07-03 3:21 ` Dave Chinner
2012-07-03 5:53 ` Mike Snitzer
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=20120703012628.GA5710@redhat.com \
--to=snitzer@redhat.com \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=xfs@oss.sgi.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).