From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.cz>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 5.12-rc2
Date: Mon, 1 Mar 2021 14:44:16 +0100 [thread overview]
Message-ID: <cover.1614605230.git.dsterba@suse.com> (raw)
From: David Sterba <dsterba@suse.cz>
Hi,
first batch of fixes that usually arrive during the merge window code
freeze. Regressions and stable material. Please pull, thanks.
Regressions:
- fix deadlock in log sync in zoned mode
- fix bugs in subpage mode still wrongly assuming sectorsize == page
size
Fixes:
- fix missing kunmap of the Q stripe in RAID6
- block group fixes:
- fix race between extent freeing/allocation when using bitmaps
- avoid double put of block group when emptying cluster
- swapfile fixes:
- fix swapfile writes vs running scrub
- fix swapfile activation vs snapshot creation
- fix stale data exposure after cloning a hole with NO_HOLES enabled
- remove tree-checker check that does not work in case information from
other leaves is necessary
----------------------------------------------------------------
The following changes since commit 9d294a685fbcb256ce8c5f7fd88a7596d0f52a8a:
btrfs: zoned: enable to mount ZONED incompat flag (2021-02-09 02:52:24 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.12-rc1-tag
for you to fetch changes up to 6e37d245994189ba757df7dc2950a44d31421ac6:
btrfs: zoned: fix deadlock on log sync (2021-02-22 18:08:48 +0100)
----------------------------------------------------------------
Filipe Manana (4):
btrfs: avoid checking for RO block group twice during nocow writeback
btrfs: fix race between writes to swap files and scrub
btrfs: fix race between swap file activation and snapshot creation
btrfs: fix stale data exposure after cloning a hole with NO_HOLES enabled
Ira Weiny (1):
btrfs: fix raid6 qstripe kmap
Johannes Thumshirn (1):
btrfs: zoned: fix deadlock on log sync
Josef Bacik (2):
btrfs: tree-checker: do not error out if extent ref hash doesn't match
btrfs: avoid double put of block group when emptying cluster
Nikolay Borisov (1):
btrfs: fix race between extent freeing/allocation when using bitmaps
Qu Wenruo (2):
btrfs: make btrfs_submit_compressed_read() subpage compatible
btrfs: make check_compressed_csum() to be subpage compatible
fs/btrfs/block-group.c | 33 +++++++++++++++++++++++-
fs/btrfs/block-group.h | 9 +++++++
fs/btrfs/compression.c | 62 +++++++++++++++++++++++++++++++--------------
fs/btrfs/ctree.h | 5 ++++
fs/btrfs/free-space-cache.c | 14 +++++-----
fs/btrfs/inode.c | 44 +++++++++++++++++++++++++++-----
fs/btrfs/raid56.c | 21 ++++++++-------
fs/btrfs/reflink.c | 18 +++++++++++++
fs/btrfs/scrub.c | 9 ++++++-
fs/btrfs/tree-checker.c | 16 +++---------
fs/btrfs/tree-log.c | 3 ---
11 files changed, 175 insertions(+), 59 deletions(-)
next reply other threads:[~2021-03-01 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 13:44 David Sterba [this message]
2021-03-01 19:44 ` [GIT PULL] Btrfs updates for 5.12-rc2 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.1614605230.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=dsterba@suse.cz \
--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).