Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_efi

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_efi_item\s+slab\s+leak\s*$/: 4 ]

Total 4 documents matching your query.

1. xfs_efi_item slab leak (score: 1): Author: Nick Piggin <npiggin@xxxxxxxxx>; Date: Sat, 18 Dec 2010 05:04:40 +1100; After running xfstests and then unmounting and rmmodding xfs, I get this bug [ 3473.194517] == [ 3473.194697] BUG xfs_efi_item: Objects remaining on kmem_cache_close() [ 3473.194793] -- [ 3473.194794; /archives/xfs/2010-12/msg00280.html (9,566 bytes)
2. Re: xfs_efi_item slab leak (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Sat, 18 Dec 2010 11:02:45 +1100; Ok, after unmounting everything I can see two items in remaining in the xfs_efi_item cache after an xfstests run. t's probably to do with a filesystem shutdown not cleaning them up correctly. I'll pu; /archives/xfs/2010-12/msg00283.html (10,213 bytes)
3. Re: xfs_efi_item slab leak (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 20 Dec 2010 06:31:39 -0500; Does it still happen with your working tree? The incorrect handling of IOP_UNPING with remove == 1 looks like it could cause something similar.; /archives/xfs/2010-12/msg00304.html (7,922 bytes)
4. Re: xfs_efi_item slab leak (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 21 Dec 2010 11:54:05 +1100; I haven't checked the current patch set - just on the kernel that I was currently running - I'll do more analysis later this afternoon. I agree that the IOP_UNPIN() handling is a likely culprit, thou; /archives/xfs/2010-12/msg00318.html (8,554 bytes)

Current List: 1 - 4
Page: [1]