linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix deadlock when enabling quotas due to concurrent snapshot creation
Date: Mon, 19 Nov 2018 12:07:08 +0200	[thread overview]
Message-ID: <a680ba06-ec55-8b48-7ed8-b1c579e34fab@suse.com> (raw)
In-Reply-To: <20181119094823.27346-1-fdmanana@kernel.org>



On 19.11.18 г. 11:48 ч., fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> If the quota enable and snapshot creation ioctls are called concurrently
> we can get into a deadlock where the task enabling quotas will deadlock
> on the fs_info->qgroup_ioctl_lock mutex because it attempts to lock it
> twice. The following time diagram shows how this happens.
> 
>            CPU 0                                    CPU 1
> 
>  btrfs_ioctl()
>   btrfs_ioctl_quota_ctl()
>    btrfs_quota_enable()
>     mutex_lock(fs_info->qgroup_ioctl_lock)
>     btrfs_start_transaction()
> 
>                                              btrfs_ioctl()
>                                               btrfs_ioctl_snap_create_v2
>                                                create_snapshot()
>                                                 --> adds snapshot to the
>                                                     list pending_snapshots
>                                                     of the current
>                                                     transaction
> 
>     btrfs_commit_transaction()
>      create_pending_snapshots()
>        create_pending_snapshot()
>         qgroup_account_snapshot()
>          btrfs_qgroup_inherit()
> 	   mutex_lock(fs_info->qgroup_ioctl_lock)
> 	    --> deadlock, mutex already locked
> 	        by this task at
> 		btrfs_quota_enable()
> 
> So fix this by adding a flag to the transaction handle that signals if the
> transaction is being used for enabling quotas (only seen by the task doing
> it) and do not lock the mutex qgroup_ioctl_lock at btrfs_qgroup_inherit()
> if the transaction handle corresponds to the one being used to enable the
> quotas.
> 
> Fixes: 6426c7ad697d ("btrfs: qgroup: Fix qgroup accounting when creating snapshot")
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
>  fs/btrfs/qgroup.c      | 10 ++++++++--
>  fs/btrfs/transaction.h |  1 +
>  2 files changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
> index d4917c0cddf5..3aec3bfa3d70 100644
> --- a/fs/btrfs/qgroup.c
> +++ b/fs/btrfs/qgroup.c
> @@ -908,6 +908,7 @@ int btrfs_quota_enable(struct btrfs_fs_info *fs_info)
>  		trans = NULL;
>  		goto out;
>  	}
> +	trans->enabling_quotas = true;
>  
>  	fs_info->qgroup_ulist = ulist_alloc(GFP_KERNEL);
>  	if (!fs_info->qgroup_ulist) {
> @@ -2250,7 +2251,11 @@ int btrfs_qgroup_inherit(struct btrfs_trans_handle *trans, u64 srcid,
>  	u32 level_size = 0;
>  	u64 nums;
>  
> -	mutex_lock(&fs_info->qgroup_ioctl_lock);
> +	if (trans->enabling_quotas)
> +		lockdep_assert_held(&fs_info->qgroup_ioctl_lock);
> +	else
> +		mutex_lock(&fs_info->qgroup_ioctl_lock);
> +

nit: That's a bit ugly for my taste, but I don't think the 
alternative is any better: 

ASSERT((trans->enabling_quotas && !lockdep_assert_held(&fs_info->qgroup_ioctl_lock)) || !trans->enabling_quotas)

if (!trans->enabling_quotas)
	mutex_lock(...)


>  	if (!test_bit(BTRFS_FS_QUOTA_ENABLED, &fs_info->flags))
>  		goto out;
>  
> @@ -2413,7 +2418,8 @@ int btrfs_qgroup_inherit(struct btrfs_trans_handle *trans, u64 srcid,
>  unlock:
>  	spin_unlock(&fs_info->qgroup_lock);
>  out:
> -	mutex_unlock(&fs_info->qgroup_ioctl_lock);
> +	if (!trans->enabling_quotas)
> +		mutex_unlock(&fs_info->qgroup_ioctl_lock);
>  	return ret;
>  }
>  
> diff --git a/fs/btrfs/transaction.h b/fs/btrfs/transaction.h
> index 703d5116a2fc..a5553a1dee30 100644
> --- a/fs/btrfs/transaction.h
> +++ b/fs/btrfs/transaction.h
> @@ -122,6 +122,7 @@ struct btrfs_trans_handle {
>  	bool reloc_reserved;
>  	bool sync;
>  	bool dirty;
> +	bool enabling_quotas;
>  	struct btrfs_root *root;
>  	struct btrfs_fs_info *fs_info;
>  	struct list_head new_bgs;
> 

  reply	other threads:[~2018-11-19 10:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  9:48 [PATCH] Btrfs: fix deadlock when enabling quotas due to concurrent snapshot creation fdmanana
2018-11-19 10:07 ` Nikolay Borisov [this message]
2018-11-19 11:09 ` Qu Wenruo
2018-11-19 11:13   ` Filipe Manana
2018-11-19 11:35     ` Qu Wenruo
2018-11-19 11:52       ` Filipe Manana
2018-11-19 12:14         ` Qu Wenruo
2018-11-19 14:15         ` Filipe Manana
2018-11-19 14:15 ` [PATCH v2] " fdmanana
2018-11-19 14:48   ` Qu Wenruo
2018-11-19 15:24     ` Filipe Manana
2018-11-20  0:32       ` Qu Wenruo
2018-11-22 13:12         ` David Sterba
2018-11-22 13:46           ` Qu Wenruo
2018-11-22 14:42             ` David Sterba
2018-11-19 15:36     ` Nikolay Borisov
2018-11-20  0:30       ` Qu Wenruo

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=a680ba06-ec55-8b48-7ed8-b1c579e34fab@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;
as well as URLs for NNTP newsgroup(s).