Skip to contentSkip to conversation

Btrfs updates for 5.6, part 2

GIT PULL Merged David Sterba 2 participants 2 messages Feb 3, 2020 Btrfs file system

lore
Share & tools
lore

David Sterba

author maintainer
#0 lore raw

Hi,

second batch containing fixes that arrived after the merge window freeze, mostly stable material. The top patch is fresh but addressing space reporing bug that's been bothering users and we've tested it meanwhile.

Please pull thanks.

* fix race in tree-mod-log element tracking

* fix bio flushing inside extent writepages

* fix assertion when in-memory tracking of discarded extents finds an empty tree (eg. after adding a new device)

* update logic of temporary read-only block groups to take into account overcommit

* fix some fixup worker corner cases:
- page could not go through proper COW cycle and the dirty status is lost due to page migration
- deadlock if delayed allocation is performed under page lock

* fix send emitting invalid clones within the same file

* fix statfs reporting 0 free space when global block reserve size is larger than remaining free space but there is still space for new chunks

----------------------------------------------------------------
The following changes since commit 4e19443da1941050b346f8fc4c368aa68413bc88:

btrfs: free block groups after free'ing fs trees (2020-01-23 17:24:39 +0100)

are available in the Git repository at:

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

for you to fetch changes up to d55966c4279bfc6a0cf0b32bf13f5df228a1eeb6:

btrfs: do not zero f_bavail if we have available space (2020-02-02 18:49:32 +0100)

----------------------------------------------------------------
Chris Mason (1):
Btrfs: keep pages dirty when using btrfs_writepage_fixup_worker

Filipe Manana (2):
Btrfs: fix race between adding and putting tree mod seq elements and nodes
Btrfs: send, fix emission of invalid clone operations within the same file

Josef Bacik (6):
btrfs: flush write bio if we loop in extent_write_cache_pages
btrfs: fix force usage in inc_block_group_ro
btrfs: take overcommit into account in inc_block_group_ro
btrfs: drop the -EBUSY case in __extent_writepage_io
btrfs: do not do delalloc reservation under page lock
btrfs: do not zero f_bavail if we have available space

Nikolay Borisov (1):
btrfs: Correctly handle empty trees in find_first_clear_extent_bit

 fs/btrfs/block-group.c           |  39 +++++++++----
 fs/btrfs/ctree.c                 |   8 +--
 fs/btrfs/ctree.h                 |   6 +-
 fs/btrfs/delayed-ref.c           |   8 +--
 fs/btrfs/disk-io.c               |   1 -
 fs/btrfs/extent_io.c             |  49 +++++++++-------
 fs/btrfs/inode.c                 | 121 +++++++++++++++++++++++++++++++--------
 fs/btrfs/send.c                  |   3 +-
 fs/btrfs/space-info.c            |  18 +++---
 fs/btrfs/space-info.h            |   3 +
 fs/btrfs/super.c                 |  10 +++-
 fs/btrfs/tests/btrfs-tests.c     |   1 -
 fs/btrfs/tests/extent-io-tests.c |   9 +++
 13 files changed, 193 insertions(+), 83 deletions(-)