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 c
tz kernel: [] ?
> mntput_no_expire+0x13/0x11c
> Jul 2 12:43:25 zertz kernel: [] ? filp_close+0x56/0x5d
> Jul 2 12:43:25 zertz kernel: [] ?
> system_call_fastpath+0x16/0x1b
> Jul 2 12:43:25 zertz kernel: INFO: Object 0x8800071d6250 @offset=592
> Jul 2 12:43:25 zertz kerne
2:43:25 zertz kernel: [] ? filp_close+0x56/0x5d
Jul 2 12:43:25 zertz kernel: [] ?
system_call_fastpath+0x16/0x1b
Jul 2 12:43:25 zertz kernel: INFO: Object 0x8800071d6250 @offset=592
Jul 2 12:43:25 zertz kernel: SLUB btrfs_transaction_cache: kmem_cache_destroy
called for cache that still has objects.
J
250 @offset=592
> SLUB btrfs_transaction_cache: kmem_cache_destroy called for
> cache that still has objects.
>
>
> This had no bad consequences (I hope), but may interest the
> developers. The kernel is
>
> Linux zertz 3.5.0-rc4+ #278 SMP Thu Jun 28 21:17:37 CEST
> 2
ache_close()
-
INFO: Slab 0xea1c7580 objects=27 used=1
fp=0x8800071d7e10 flags=0x40004080
INFO: Object 0x8800071d6250 @offset=592
SLUB btrfs_transaction_cache: kmem_cache_destroy called for
cache that still has objects.
This had no bad conse
