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 6.5-rc6
Date: Sat, 12 Aug 2023 21:13:52 +0200 [thread overview]
Message-ID: <cover.1691865526.git.dsterba@suse.com> (raw)
Hi,
more fixes, some of them going back to older releases and there are
fixes for hangs in stress tests regarding space caching.
- space caching hangs fixes to progress stracking, found by test
generic/475
- writeback fixes, write pages in integrity mode and skip writing pages
that have been written meanwhile
- properly clear end of extent range after an error
- relocation fixes
- fix race betwen qgroup tree creation and relocation
- detect and report invalid reloc roots
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit b28ff3a7d7e97456fd86b68d24caa32e1cfa7064:
btrfs: check for commit error at btrfs_attach_transaction_barrier() (2023-07-26 13:57:47 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.5-rc5-tag
for you to fetch changes up to 92fb94b69c6accf1e49fff699640fa0ce03dc910:
btrfs: set cache_block_group_error if we find an error (2023-08-10 17:16:45 +0200)
----------------------------------------------------------------
Christoph Hellwig (3):
btrfs: don't stop integrity writeback too early
btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
btrfs: properly clear end of the unreserved range in cow_file_range
Josef Bacik (2):
btrfs: wait for actual caching progress during allocation
btrfs: set cache_block_group_error if we find an error
Qu Wenruo (3):
btrfs: avoid race between qgroup tree creation and relocation
btrfs: exit gracefully if reloc roots don't match
btrfs: reject invalid reloc tree root keys with stack dump
fs/btrfs/block-group.c | 17 +++++++++++++++--
fs/btrfs/block-group.h | 2 ++
fs/btrfs/disk-io.c | 13 ++++++++++++-
fs/btrfs/extent-tree.c | 5 ++++-
fs/btrfs/extent_io.c | 13 ++++++++++---
fs/btrfs/inode.c | 10 +++++-----
fs/btrfs/relocation.c | 45 +++++++++++++++++++++++++++++++++++++--------
fs/btrfs/tree-checker.c | 14 ++++++++++++++
8 files changed, 99 insertions(+), 20 deletions(-)
next reply other threads:[~2023-08-12 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 19:13 David Sterba [this message]
2023-08-12 20:36 ` [GIT PULL] Btrfs fixes for 6.5-rc6 Linus Torvalds
2023-08-16 17:04 ` Nikolay Borisov
2023-08-12 20:37 ` 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.1691865526.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.