diff options
| author | Filipe Manana <fdmanana@suse.com> | 2015-06-13 08:52:56 +0300 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2015-07-01 00:36:46 +0300 |
| commit | c3f4a1685bb87e59c886ee68f7967eae07d4dffa (patch) | |
| tree | 9337b53985de5c9010d75c82d9c34148c493e708 /fs/btrfs | |
| parent | 67c5e7d464bc466471b05e027abe8a6b29687ebd (diff) | |
| download | linux-c3f4a1685bb87e59c886ee68f7967eae07d4dffa.tar.xz | |
Btrfs: use kmem_cache_free when freeing entry in inode cache
The free space entries are allocated using kmem_cache_zalloc(),
through __btrfs_add_free_space(), therefore we should use
kmem_cache_free() and not kfree() to avoid any confusion and
any potential problem. Looking at the kfree() definition at
mm/slab.c it has the following comment:
/*
* (...)
*
* Don't free memory not originally allocated by kmalloc()
* or you will run into trouble.
*/
So better be safe and use kmem_cache_free().
Cc: stable@vger.kernel.org
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/btrfs')
| -rw-r--r-- | fs/btrfs/inode-map.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/inode-map.c b/fs/btrfs/inode-map.c index f6a596d5a637..218df701e607 100644 --- a/fs/btrfs/inode-map.c +++ b/fs/btrfs/inode-map.c @@ -271,7 +271,7 @@ void btrfs_unpin_free_ino(struct btrfs_root *root) __btrfs_add_free_space(ctl, info->offset, count); free: rb_erase(&info->offset_index, rbroot); - kfree(info); + kmem_cache_free(btrfs_free_space_cachep, info); } } |