author | Chris Mason <clm@fb.com> | |
Tue, 4 Nov 2014 14:59:04 +0000 (06:59 -0800) | ||
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
Fri, 14 Nov 2014 16:48:01 +0000 (08:48 -0800) | ||
commit | 58f382ffaf2570032da636a348aa6c045a166f4e | |
tree | e0111ae2df000bdea4660008bb91a802036136bb | tree | snapshot (tar.xz tar.gz zip) |
parent | 96db973853b1d5a93836261b0edcc877ddc335a4 | commit | diff |
Btrfs: fix kfree on list_head in btrfs_lookup_csums_range error cleanup
commit 6e5aafb27419f32575b27ef9d6a31e5d54661aca upstream.
If we hit any errors in btrfs_lookup_csums_range, we'll loop through all
the csums we allocate and free them. But the code was using list_entry
incorrectly, and ended up trying to free the on-stack list_head instead.
This bug came from commit 0678b6185
btrfs: Don't BUG_ON kzalloc error in btrfs_lookup_csums_range()
Signed-off-by: Chris Mason <clm@fb.com>
Reported-by: Erik Berg <btrfs@slipsprogrammoer.no>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 6e5aafb27419f32575b27ef9d6a31e5d54661aca upstream.
If we hit any errors in btrfs_lookup_csums_range, we'll loop through all
the csums we allocate and free them. But the code was using list_entry
incorrectly, and ended up trying to free the on-stack list_head instead.
This bug came from commit 0678b6185
btrfs: Don't BUG_ON kzalloc error in btrfs_lookup_csums_range()
Signed-off-by: Chris Mason <clm@fb.com>
Reported-by: Erik Berg <btrfs@slipsprogrammoer.no>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/btrfs/file-item.c | diff | blob | history |