From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 5.6, part 2
Date: Mon, 3 Feb 2020 16:38:55 +0100 [thread overview]
Message-ID: <cover.1580742376.git.dsterba@suse.com> (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(-)
next reply other threads:[~2020-02-03 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 15:38 David Sterba [this message]
2020-02-03 17:20 ` [GIT PULL] Btrfs updates for 5.6, part 2 pr-tracker-bot
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=cover.1580742376.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).