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.11-rc2
Date: Wed, 31 Jul 2024 04:14:09 +0200 [thread overview]
Message-ID: <cover.1722390813.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes, thanks.
- fix regression in extent map rework when handling insertion of
overlapping compressed extent
- fix unexpected file length when appending to a file using direct io
and buffer not faulted in
- in zoned mode, fix accounting of unusable space when flipping
read-only block group back to read-write
- fix page locking when COWing an inline range, assertion failure found
by syzbot
- fix calculation of space info in debugging print
- tree-checker, add validation of data reference item
- fix a few -Wmaybe-uninitialized build warnings
----------------------------------------------------------------
The following changes since commit c3ece6b7ffb4a7c00e8d53cbf4026a32b6127914:
btrfs: change BTRFS_MOUNT_* flags to 64bit type (2024-07-19 17:20:23 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.11-rc1-tag
for you to fetch changes up to b8e947e9f64cac9df85a07672b658df5b2bcff07:
btrfs: initialize location to fix -Wmaybe-uninitialized in btrfs_lookup_dentry() (2024-07-30 15:33:06 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: make cow_file_range_inline() honor locked_page on error
David Sterba (1):
btrfs: initialize location to fix -Wmaybe-uninitialized in btrfs_lookup_dentry()
Filipe Manana (2):
btrfs: fix corrupt read due to bad offset of a compressed extent map
btrfs: fix corruption after buffer fault in during direct IO append write
Naohiro Aota (2):
btrfs: do not subtract delalloc from avail bytes
btrfs: zoned: fix zone_unusable accounting on making block group read-write again
Qu Wenruo (1):
btrfs: tree-checker: validate dref root and objectid
fs/btrfs/block-group.c | 13 +++--
fs/btrfs/ctree.h | 1 +
fs/btrfs/direct-io.c | 38 +++++++++++----
fs/btrfs/extent-tree.c | 3 +-
fs/btrfs/extent_map.c | 2 +-
fs/btrfs/file.c | 17 +++++--
fs/btrfs/free-space-cache.c | 4 +-
fs/btrfs/inode.c | 18 ++++---
fs/btrfs/space-info.c | 5 +-
fs/btrfs/space-info.h | 1 +
fs/btrfs/tests/extent-map-tests.c | 99 +++++++++++++++++++++++++++++++++++++++
fs/btrfs/tree-checker.c | 47 +++++++++++++++++++
include/trace/events/btrfs.h | 8 ++++
13 files changed, 225 insertions(+), 31 deletions(-)
next reply other threads:[~2024-07-31 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 2:14 David Sterba [this message]
2024-07-31 2:43 ` [GIT PULL] Btrfs fixes for 6.11-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.1722390813.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.