From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: xfs_btree_cur leak with 3.5-rc4 Date: Mon, 2 Jul 2012 21:26:28 -0400 Message-ID: <20120703012628.GA5710@redhat.com> References: <20120702191412.GA3617@redhat.com> <20120703002611.GW19223@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120703002611.GW19223@dastard> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: dm-devel@redhat.com, xfs@oss.sgi.com List-Id: dm-devel.ids On Mon, Jul 02 2012 at 8:26pm -0400, Dave Chinner 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