Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Ioannis Angelakopoulos <iangelak@fb.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [RFC PATCH 2/2] btrfs: Lockdep annotations for the extent bits wait event
Date: Tue, 23 Aug 2022 23:02:50 +0200	[thread overview]
Message-ID: <20220823210250.GV13489@twin.jikos.cz> (raw)
In-Reply-To: <20220812004241.1722846-3-iangelak@fb.com>

On Thu, Aug 11, 2022 at 05:42:44PM -0700, Ioannis Angelakopoulos wrote:
> Add lockdep annotations in five places that lock extent bits:
>   1) find_lock_delalloc_range() in fs/btrfs/extent_io.c and its callers
>   2) btrfs_lock_and_flush_ordered_range() in fs/btrfs/ordered-data.c and
>   its callers
>   3) extent_fiemap() in fs/btrfs/extent_io.c
>   4) btrfs_fallocate() in fs/btrfs/file.c
>   5) btrfs_finish_ordered_io() in fs/btrfs/inode.c
> 
> To annotate the extent bits wait event we make use of a two level lockdep
> map (making use of the multilevel wait event lockdep annotation macros).
> The first level is used for high level functions such as btrfs_fallocate()
> and the second level is used for low level functions, such as
> find_lock_delalloc_range().
> 
> If we used only one level then lockdep would complain because there are
> execution contexts where the extent bits annotation is acquired before the
> delalloc_mutex (i.e., in btrfs_fallocate()) and later delalloc_mutex is
> acquired before the extent bits annotation (i.e.,
> find_lock_delalloc_range()). Normally, if the range of bits locked were the
> same for both btrfs_fallocate() and find_lock_delalloc_range() we would
> have a deadlock(). However, a call to btrfs_wait_ordered_range() from
> btrfs_fallocate() guarantees that the range of extent bits is unlocked
> before locking, thus the deadlock is averted.
> 
> By using a two level lockdep map we "break" the dependency between the high
> and low levels, thus lockdep does not complain.
> 
> Signed-off-by: Ioannis Angelakopoulos <iangelak@fb.com>
> ---
>  fs/btrfs/ctree.h        |   1 +
>  fs/btrfs/disk-io.c      |   1 +
>  fs/btrfs/extent_io.c    | 114 +++++++++++++++++++++++++++++++++++++---
>  fs/btrfs/file.c         |  10 ++--
>  fs/btrfs/inode.c        |  22 ++++++--
>  fs/btrfs/ordered-data.c |   4 +-
>  6 files changed, 133 insertions(+), 19 deletions(-)
> 
> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> index 44837545eef8..85f947ce6e6b 100644
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -1104,6 +1104,7 @@ struct btrfs_fs_info {
>  	struct lockdep_map btrfs_state_change_map[4];
>  	struct lockdep_map btrfs_trans_pending_ordered_map;
>  	struct lockdep_map btrfs_ordered_extent_map;
> +	struct lockdep_map btrfs_inode_extent_lock_map;
>  
>  #ifdef CONFIG_BTRFS_FS_REF_VERIFY
>  	spinlock_t ref_verify_lock;
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 6268dafeeb2d..afd971c31168 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2996,6 +2996,7 @@ void btrfs_init_fs_info(struct btrfs_fs_info *fs_info)
>  	btrfs_lockdep_init_map(fs_info, btrfs_trans_num_extwriters);
>  	btrfs_lockdep_init_map(fs_info, btrfs_trans_pending_ordered);
>  	btrfs_lockdep_init_map(fs_info, btrfs_ordered_extent);
> +	btrfs_lockdep_init_map(fs_info, btrfs_inode_extent_lock);
>  	btrfs_state_lockdep_init_map(fs_info, btrfs_trans_commit_start,
>  				     BTRFS_LOCKDEP_TRANS_COMMIT_START);
>  	btrfs_state_lockdep_init_map(fs_info, btrfs_trans_unblocked,
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index 6e8e936a8a1e..3d2ef3d78e7f 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -891,6 +891,24 @@ int __clear_extent_bit(struct extent_io_tree *tree, u64 start, u64 end,
>  
>  }
>  
> +int __clear_extent_bit_lockdep(struct extent_io_tree *tree, u64 start, u64 end,
> +			       u32 bits, int wake, int delete,
> +			       struct extent_state **cached_state,
> +			       gfp_t mask, struct extent_changeset *changeset)
> +{
> +	int ret;
> +
> +	ret = __clear_extent_bit(tree, start, end, bits, wake, delete, cached_state,
> +				 mask, changeset);
> +
> +	if ((tree->owner != IO_TREE_FREE_SPACE_INODE_IO) &&
> +	    (tree->owner == IO_TREE_INODE_IO))
> +		btrfs_lockdep_release(tree->fs_info, btrfs_inode_extent_lock);
> +
> +	return ret;
> +}
> +
> +
>  static void wait_on_state(struct extent_io_tree *tree,
>  			  struct extent_state *state)
>  		__releases(tree->lock)
> @@ -1470,6 +1488,14 @@ int clear_extent_bit(struct extent_io_tree *tree, u64 start, u64 end,
>  				  cached, GFP_NOFS, NULL);
>  }
>  
> +int clear_extent_bit_lockdep(struct extent_io_tree *tree, u64 start, u64 end,
> +			     u32 bits, int wake, int delete,
> +			     struct extent_state **cached)
> +{
> +	return __clear_extent_bit_lockdep(tree, start, end, bits, wake, delete,
> +					  cached, GFP_NOFS, NULL);
> +}
> +
>  int clear_record_extent_bits(struct extent_io_tree *tree, u64 start, u64 end,
>  		u32 bits, struct extent_changeset *changeset)
>  {
> @@ -1504,6 +1530,43 @@ int lock_extent_bits(struct extent_io_tree *tree, u64 start, u64 end,
>  			break;
>  		WARN_ON(start > end);
>  	}
> +
> +	return err;
> +}
> +
> +int lock_extent_bits_lockdep(struct extent_io_tree *tree, u64 start, u64 end,
> +			     struct extent_state **cached_state, bool nested)
> +{
> +	int err;
> +#ifdef CONFIG_LOCKDEP
> +	int subclass = 1;
> +#endif

Does this compile with lockdep disabled?

> +
> +	/* The wait event occurs within lock_extent_bits() */
> +	if ((tree->owner != IO_TREE_FREE_SPACE_INODE_IO) &&
> +	    (tree->owner == IO_TREE_INODE_IO)) {
> +		if (nested)
> +			btrfs_might_wait_for_event_nested(tree->fs_info,
> +							  btrfs_inode_extent_lock,
> +							  subclass);

it's used here

> +		else
> +			btrfs_might_wait_for_event(tree->fs_info,
> +						   btrfs_inode_extent_lock);
> +	}
> +
> +	err = lock_extent_bits(tree, start, end, cached_state);
> +
> +	if ((tree->owner != IO_TREE_FREE_SPACE_INODE_IO) &&
> +	    (tree->owner == IO_TREE_INODE_IO)) {
> +		if (nested)
> +			btrfs_lockdep_acquire_nested(tree->fs_info,
> +						     btrfs_inode_extent_lock,
> +						     subclass);

and here

> +		else
> +			btrfs_lockdep_acquire(tree->fs_info,
> +					      btrfs_inode_extent_lock);
> +	}
> +
>  	return err;
>  }

      reply	other threads:[~2022-08-23 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  0:42 [RFC PATCH 0/2] btrfs: Add a lockdep annotation for the extent bits wait event Ioannis Angelakopoulos
2022-08-12  0:42 ` [RFC PATCH 1/2] btrfs: Add lockdep wrappers around the extent bits locking and unlocking functions Ioannis Angelakopoulos
2022-08-12  0:42 ` [RFC PATCH 2/2] btrfs: Lockdep annotations for the extent bits wait event Ioannis Angelakopoulos
2022-08-23 21:02   ` David Sterba [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=20220823210250.GV13489@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=iangelak@fb.com \
    --cc=kernel-team@fb.com \
    --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