From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.18-rc5
Date: Tue, 26 Apr 2022 14:46:29 +0200 [thread overview]
Message-ID: <cover.1650923679.git.dsterba@suse.com> (raw)
Hi,
a few more fixes, please pull, thanks.
- direct IO fixes:
- restore passing file offset to correctly calculate checksums when
repairing on read and bio split happens
- use correct bio when sumitting IO on zoned filesystem
- zoned mode fixes:
- fix selection of device to correctly calculate device capabilities
when allocating a new bio
- use a dedicated lock for exclusion during relocation
- fix leaked plug after failure syncing log
- fix assertion during scrub and relocation
----------------------------------------------------------------
The following changes since commit acee08aaf6d158d03668dc82b0a0eef41100531b:
btrfs: fix btrfs_submit_compressed_write cgroup attribution (2022-04-06 00:50:51 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.18-rc4-tag
for you to fetch changes up to 5f0addf7b89085f8e0a2593faa419d6111612b9b:
btrfs: zoned: use dedicated lock for data relocation (2022-04-21 16:06:24 +0200)
----------------------------------------------------------------
Christoph Hellwig (3):
btrfs: fix and document the zoned device choice in alloc_new_bio
btrfs: fix direct I/O read repair for split bios
btrfs: fix direct I/O writes for split bios on zoned devices
Filipe Manana (2):
btrfs: fix leaked plug after failure syncing log on zoned filesystems
btrfs: fix assertion failure during scrub due to block group reallocation
Naohiro Aota (1):
btrfs: zoned: use dedicated lock for data relocation
fs/btrfs/ctree.h | 1 +
fs/btrfs/dev-replace.c | 7 ++++++-
fs/btrfs/disk-io.c | 1 +
fs/btrfs/extent_io.c | 44 +++++++++++++++++++++++++++++---------------
fs/btrfs/inode.c | 18 ++++++++----------
fs/btrfs/scrub.c | 26 +++++++++++++++++++++++++-
fs/btrfs/tree-log.c | 1 +
fs/btrfs/volumes.h | 3 +++
fs/btrfs/zoned.h | 4 ++--
9 files changed, 76 insertions(+), 29 deletions(-)
next reply other threads:[~2022-04-26 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 12:46 David Sterba [this message]
2022-04-26 19:06 ` [GIT PULL] Btrfs fixes for 5.18-rc5 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.1650923679.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