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 fixes for v5.13-rc3, part 2
Date: Fri, 21 May 2021 22:11:13 +0200 [thread overview]
Message-ID: <cover.1621627293.git.dsterba@suse.com> (raw)
Hi,
a few more fixes. Please pull, thanks.
- fix unaligned compressed writes in zoned mode
- fix false positive lockdep warning when cloning inline extent
- remove wrong BUG_ON in tree-log error handling
----------------------------------------------------------------
The following changes since commit 54a40fc3a1da21b52dbf19f72fdc27a2ec740760:
btrfs: fix removed dentries still existing after log is synced (2021-05-14 01:23:04 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.13-rc2-tag
for you to fetch changes up to 764c7c9a464b68f7c6a5a9ec0b923176a05e8e8f:
btrfs: zoned: fix parallel compressed writes (2021-05-20 15:51:07 +0200)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: release path before starting transaction when cloning inline extent
Johannes Thumshirn (2):
btrfs: zoned: pass start block to btrfs_use_zone_append
btrfs: zoned: fix parallel compressed writes
Josef Bacik (1):
btrfs: do not BUG_ON in link_to_fixup_dir
fs/btrfs/compression.c | 42 ++++++++++++++++++++++++++++++++++++++----
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/inode.c | 2 +-
fs/btrfs/reflink.c | 5 +++++
fs/btrfs/tree-log.c | 2 --
fs/btrfs/zoned.c | 4 ++--
fs/btrfs/zoned.h | 5 ++---
7 files changed, 49 insertions(+), 13 deletions(-)
next reply other threads:[~2021-05-21 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 20:11 David Sterba [this message]
2021-05-21 23:31 ` [GIT PULL] Btrfs fixes for v5.13-rc3, 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.1621627293.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