public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/5] Btrfs: fix inode cache waiters hanging on path allocation failure
Date: Mon, 8 Jul 2019 09:20:54 +0300	[thread overview]
Message-ID: <537d6c99-5cef-3148-2379-5f76c9ce1e56@suse.com> (raw)
In-Reply-To: <20190704152444.20815-1-fdmanana@kernel.org>



On 4.07.19 г. 18:24 ч., fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> 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")
> Signed-off-by: Filipe Manana <fdmanana@suse.com>

Reviewed-by: Nikolay Borisov <nborisov@suse.com>

> ---
>  fs/btrfs/inode-map.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/inode-map.c b/fs/btrfs/inode-map.c
> index 05b8c9927f29..4820e05ea6bd 100644
> --- a/fs/btrfs/inode-map.c
> +++ b/fs/btrfs/inode-map.c
> @@ -41,8 +41,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;
> 

      parent reply	other threads:[~2019-07-08  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 15:24 [PATCH 4/5] Btrfs: fix inode cache waiters hanging on path allocation failure fdmanana
2019-07-08  6:13 ` Nikolay Borisov
2019-07-08  6:20 ` Nikolay Borisov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537d6c99-5cef-3148-2379-5f76c9ce1e56@suse.com \
    --to=nborisov@suse.com \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox