* [PATCH] btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range
@ 2019-07-26 7:47 Naohiro Aota
2019-07-26 8:49 ` Nikolay Borisov
2019-07-26 10:33 ` David Sterba
0 siblings, 2 replies; 3+ messages in thread
From: Naohiro Aota @ 2019-07-26 7:47 UTC (permalink / raw)
To: linux-btrfs; +Cc: David Sterba, Nikolay Borisov, Naohiro Aota
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")
Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
---
fs/btrfs/ordered-data.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/fs/btrfs/ordered-data.c b/fs/btrfs/ordered-data.c
index df02ed25b7db..ab31b1a1b624 100644
--- a/fs/btrfs/ordered-data.c
+++ b/fs/btrfs/ordered-data.c
@@ -982,13 +982,14 @@ void btrfs_lock_and_flush_ordered_range(struct extent_io_tree *tree,
struct extent_state **cached_state)
{
struct btrfs_ordered_extent *ordered;
- struct extent_state *cachedp = NULL;
+ struct extent_state *cache = NULL;
+ struct extent_state **cachedp = &cache;
if (cached_state)
- cachedp = *cached_state;
+ cachedp = cached_state;
while (1) {
- lock_extent_bits(tree, start, end, &cachedp);
+ lock_extent_bits(tree, start, end, cachedp);
ordered = btrfs_lookup_ordered_range(inode, start,
end - start + 1);
if (!ordered) {
@@ -998,10 +999,10 @@ void btrfs_lock_and_flush_ordered_range(struct extent_io_tree *tree,
* aren't exposing it outside of this function
*/
if (!cached_state)
- refcount_dec(&cachedp->refs);
+ refcount_dec(&cache->refs);
break;
}
- unlock_extent_cached(tree, start, end, &cachedp);
+ unlock_extent_cached(tree, start, end, cachedp);
btrfs_start_ordered_extent(&inode->vfs_inode, ordered, 1);
btrfs_put_ordered_extent(ordered);
}
--
2.22.0
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range
2019-07-26 7:47 [PATCH] btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range Naohiro Aota
@ 2019-07-26 8:49 ` Nikolay Borisov
2019-07-26 10:33 ` David Sterba
1 sibling, 0 replies; 3+ messages in thread
From: Nikolay Borisov @ 2019-07-26 8:49 UTC (permalink / raw)
To: Naohiro Aota, linux-btrfs; +Cc: David Sterba
On 26.07.19 г. 10:47 ч., Naohiro Aota wrote:
> 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")
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/ordered-data.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/fs/btrfs/ordered-data.c b/fs/btrfs/ordered-data.c
> index df02ed25b7db..ab31b1a1b624 100644
> --- a/fs/btrfs/ordered-data.c
> +++ b/fs/btrfs/ordered-data.c
> @@ -982,13 +982,14 @@ void btrfs_lock_and_flush_ordered_range(struct extent_io_tree *tree,
> struct extent_state **cached_state)
> {
> struct btrfs_ordered_extent *ordered;
> - struct extent_state *cachedp = NULL;
> + struct extent_state *cache = NULL;
> + struct extent_state **cachedp = &cache;
>
> if (cached_state)
> - cachedp = *cached_state;
> + cachedp = cached_state;
>
> while (1) {
> - lock_extent_bits(tree, start, end, &cachedp);
> + lock_extent_bits(tree, start, end, cachedp);
> ordered = btrfs_lookup_ordered_range(inode, start,
> end - start + 1);
> if (!ordered) {
> @@ -998,10 +999,10 @@ void btrfs_lock_and_flush_ordered_range(struct extent_io_tree *tree,
> * aren't exposing it outside of this function
> */
> if (!cached_state)
> - refcount_dec(&cachedp->refs);
> + refcount_dec(&cache->refs);
> break;
> }
> - unlock_extent_cached(tree, start, end, &cachedp);
> + unlock_extent_cached(tree, start, end, cachedp);
> btrfs_start_ordered_extent(&inode->vfs_inode, ordered, 1);
> btrfs_put_ordered_extent(ordered);
> }
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range
2019-07-26 7:47 [PATCH] btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range Naohiro Aota
2019-07-26 8:49 ` Nikolay Borisov
@ 2019-07-26 10:33 ` David Sterba
1 sibling, 0 replies; 3+ messages in thread
From: David Sterba @ 2019-07-26 10:33 UTC (permalink / raw)
To: Naohiro Aota; +Cc: linux-btrfs, David Sterba, Nikolay Borisov
On Fri, Jul 26, 2019 at 04:47:05PM +0900, Naohiro Aota wrote:
> 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")
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Queued for 5.3, thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-07-26 10:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-07-26 7:47 [PATCH] btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range Naohiro Aota
2019-07-26 8:49 ` Nikolay Borisov
2019-07-26 10:33 ` David Sterba
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox