diff options
| author | Naohiro Aota <naohiro.aota@wdc.com> | 2019-07-26 16:47:05 +0900 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2019-07-26 12:21:22 +0200 |
| commit | a3b46b86ca76d7f9d487e6a0b594fd1984e0796e (patch) | |
| tree | efab271e267efffe207b474b9959af63152f683d /fs/xfs/xfs_dquot_item.h | |
| parent | 6e7ca09b583de4be6c27d9d4b06e8c5dd46a58fa (diff) | |
| download | linux-a3b46b86ca76d7f9d487e6a0b594fd1984e0796e.tar.gz linux-a3b46b86ca76d7f9d487e6a0b594fd1984e0796e.tar.bz2 linux-a3b46b86ca76d7f9d487e6a0b594fd1984e0796e.zip | |
btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range
btrfs_lock_and_flush_ordered_range() loads given "*cached_state" into
cachedp, which, in general, is NULL. Then, lock_extent_bits() updates
"cachedp", but it never goes backs to the caller. Thus the caller still
see its "cached_state" to be NULL and never free the state allocated
under btrfs_lock_and_flush_ordered_range(). As a result, we will
see massive state leak with e.g. fstests btrfs/005. Fix this bug by
properly handling the pointers.
Fixes: bd80d94efb83 ("btrfs: Always use a cached extent_state in btrfs_lock_and_flush_ordered_range")
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/xfs/xfs_dquot_item.h')
0 files changed, 0 insertions, 0 deletions