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.13-rc4
Date: Wed, 18 Dec 2024 18:49:53 +0100 [thread overview]
Message-ID: <cover.1734477842.git.dsterba@suse.com> (raw)
Hi,
a few more fixes. This is based on 6.13-rc1 as it needs
exported bio_is_zone_append() (commit 0ef2b9e698dbf9ba78f).
Please pull, thanks.
- tree-checker catches invalid number of inline extent references
- zoned mode fixes:
- enhance zone append IO command so it also detects emulated writes
- handle bio splitting at sectorsize boundary
- when deleting a snapshot, fix a condition for visiting nodes in reloc
trees
----------------------------------------------------------------
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.13-rc3-tag
for you to fetch changes up to dfb92681a19e1d5172420baa242806414b3eff6f:
btrfs: tree-checker: reject inline extent items with 0 ref count (2024-12-17 19:54:32 +0100)
----------------------------------------------------------------
Christoph Hellwig (2):
btrfs: use bio_is_zone_append() in the completion handler
btrfs: split bios to the fs sector size boundary
Josef Bacik (1):
btrfs: fix improper generation check in snapshot delete
Qu Wenruo (1):
btrfs: tree-checker: reject inline extent items with 0 ref count
fs/btrfs/bio.c | 16 +++++++++++-----
fs/btrfs/ctree.h | 19 +++++++++++++++++++
fs/btrfs/extent-tree.c | 6 +++---
fs/btrfs/tree-checker.c | 27 ++++++++++++++++++++++++++-
4 files changed, 59 insertions(+), 9 deletions(-)
next reply other threads:[~2024-12-18 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 17:49 David Sterba [this message]
2024-12-18 22:20 ` [GIT PULL] Btrfs fixes for 6.13-rc4 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.1734477842.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.