Btrfs: fix inode cache waiters hanging on path allocation failure
authorFilipe Manana <fdmanana@suse.com>
Thu, 4 Jul 2019 15:24:44 +0000 (16:24 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 27 Jan 2020 13:46:46 +0000 (14:46 +0100)
[ Upstream commit 9d123a35d7e97bb2139747b16127c9b22b6a593e ]

If the caching thread fails to allocate a path, it returns without waking
up any cache waiters, leaving them hang forever. Fix this by following the
same approach as when we fail to start the caching thread: print an error
message, disable inode caching and make the wakers fallback to non-caching
mode behaviour (calling btrfs_find_free_objectid()).

Fixes: 581bb050941b4f ("Btrfs: Cache free inode numbers in memory")
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/btrfs/inode-map.c

index b1c3a4ec76c8c243595b3707a4ec52ae15f54a7d..2ae32451fb5b020034cc5cf47699a2004ccb5679 100644 (file)
@@ -55,8 +55,10 @@ static int caching_kthread(void *data)
                return 0;
 
        path = btrfs_alloc_path();
-       if (!path)
+       if (!path) {
+               fail_caching_thread(root);
                return -ENOMEM;
+       }
 
        /* Since the commit root is read-only, we can safely skip locking. */
        path->skip_locking = 1;