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.19-rc4, part 2
Date: Sun, 26 Jun 2022 17:30:05 +0200 [thread overview]
Message-ID: <cover.1656256131.git.dsterba@suse.com> (raw)
Hi,
a few more fixes, they have been in testing branches for last weeks.
Please pull, thanks.
- zoned relocation fixes
- fix critical section end for extent writeback, this could lead to
out of order write
- prevent writing to previous data relocation block group if space
gets low
- reflink fixes
- fix race between reflinking and ordered extent completion
- proper error handling when block reserve migration fails
- add missing inode iversion/mtime/ctime updates on each iteration
when replacing extents
- fix deadlock when running fsync/fiemap/commit at the same time
- fix KCSAN report regarding pid tracking for read locks and data race,
but that's a false alert
- minor documentation update and link to new site
----------------------------------------------------------------
The following changes since commit e3a4167c880cf889f66887a152799df4d609dd21:
btrfs: add error messages to all unrecognized mount options (2022-06-07 17:29:50 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.19-rc3-tag
for you to fetch changes up to 037e127452b973f45b34c1e88a1af183e652e657:
Documentation: update btrfs list of features and link to readthedocs.io (2022-06-21 14:47:19 +0200)
----------------------------------------------------------------
David Sterba (1):
Documentation: update btrfs list of features and link to readthedocs.io
Filipe Manana (3):
btrfs: fix race between reflinking and ordered extent completion
btrfs: add missing inode updates on each iteration when replacing extents
btrfs: do not BUG_ON() on failure to migrate space when replacing extents
Josef Bacik (1):
btrfs: fix deadlock with fsync+fiemap+transaction commit
Naohiro Aota (2):
btrfs: zoned: prevent allocation from previous data relocation BG
btrfs: zoned: fix critical section of relocation inode writeback
Zygo Blaxell (1):
btrfs: don't set lock_owner when locking extent buffer for reading
Documentation/filesystems/btrfs.rst | 16 +++++--
fs/btrfs/block-group.h | 1 +
fs/btrfs/ctree.h | 2 +
fs/btrfs/extent-tree.c | 20 +++++++-
fs/btrfs/extent_io.c | 3 +-
fs/btrfs/file.c | 92 ++++++++++++++++++++++++++++++-------
fs/btrfs/inode.c | 3 ++
fs/btrfs/locking.c | 3 --
fs/btrfs/reflink.c | 16 +++++--
fs/btrfs/zoned.c | 27 +++++++++++
fs/btrfs/zoned.h | 5 ++
11 files changed, 158 insertions(+), 30 deletions(-)
next reply other threads:[~2022-06-26 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:30 David Sterba [this message]
2022-06-26 17:36 ` [GIT PULL] Btrfs fixes for 5.19-rc4, 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.1656256131.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).