[GIT PULL] Btrfs fixes for 6.2-rc8, part 2

[David Sterba <dsterba@suse.com>]

Hi,

a few more fixes for bugs that have some user visible impact (user and
syzbot reports). Please pull, thanks.

- one more fix for a tree-log 'write time corruption' report, update
  the last dir index directly and don't keep in the log context

- do VFS-level inode lock around FIEMAP to prevent a deadlock with
  concurrent fsync, the extent-level lock is not sufficient

- don't cache a single-device filesystem device to avoid cases when a
  loop device is reformatted and the entry gets stale

----------------------------------------------------------------
The following changes since commit a9ad4d87aa263de36895402b66115a3a4b88bf1c:

  btrfs: raid56: make error_bitmap update atomic (2023-01-27 14:57:10 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.2-rc7-tag

for you to fetch changes up to 5f58d783fd7823b2c2d5954d1126e702f94bfc4c:

  btrfs: free device in btrfs_close_devices for a single device filesystem (2023-02-09 17:02:51 +0100)

----------------------------------------------------------------
Anand Jain (1):
      btrfs: free device in btrfs_close_devices for a single device filesystem

Filipe Manana (2):
      btrfs: simplify update of last_dir_index_offset when logging a directory
      btrfs: lock the inode in shared mode before starting fiemap

 fs/btrfs/extent_io.c |  2 ++
 fs/btrfs/tree-log.c  | 23 +++++++++++++++++------
 fs/btrfs/tree-log.h  |  2 --
 fs/btrfs/volumes.c   | 16 +++++++++++++++-
 4 files changed, 34 insertions(+), 9 deletions(-)