From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.15-rc4
Date: Tue, 22 Apr 2025 18:52:27 +0200 [thread overview]
Message-ID: <cover.1745339483.git.dsterba@suse.com> (raw)
Hi,
please pull the following short fixes. Most of them are one-liners,
there's one preparatory patch in block layer moving some code around
and adding a helper that's used in a fix. Thanks.
- subpage mode fixes
- access correct object (folio) when looking up bit offset
- fix assertion condition for number of blocks per folio
- fix upper boundary of locking range in hole punch
- zoned fixes
- fix potential deadlock caught by lockdep when zone reporting and
device freeze run in parallel
- fix zone write pointer mismatch and NULL pointer dereference when
metadata are converted from DUP to RAID1
- fix error handling when reloc inode creation fails
- in tree-checker, unify error code for header level check
- block layer: add helpers to read zone capacity
----------------------------------------------------------------
The following changes since commit 65f2a3b2323edde7c5de3a44e67fec00873b4217:
btrfs: remove folio order ASSERT()s in super block writeback path (2025-04-01 01:02:42 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.15-rc3-tag
for you to fetch changes up to 866bafae59ecffcf1840d846cd79740be29f21d6:
btrfs: zoned: skip reporting zone for new block group (2025-04-17 11:57:25 +0200)
----------------------------------------------------------------
David Sterba (1):
btrfs: tree-checker: adjust error code for header level check
Filipe Manana (1):
btrfs: fix invalid inode pointer after failure to create reloc inode
Johannes Thumshirn (1):
btrfs: zoned: return EIO on RAID1 block group write pointer mismatch
Naohiro Aota (2):
block: introduce zone capacity helper
btrfs: zoned: skip reporting zone for new block group
Qu Wenruo (3):
btrfs: subpage: access correct object when reading bitmap start in subpage_calc_start_bit()
btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range()
btrfs: fix the ASSERT() inside GET_SUBPAGE_BITMAP()
fs/btrfs/file.c | 9 +++++--
fs/btrfs/relocation.c | 2 +-
fs/btrfs/subpage.c | 4 +--
fs/btrfs/tree-checker.c | 2 +-
fs/btrfs/zoned.c | 19 +++++++++++---
include/linux/blkdev.h | 67 +++++++++++++++++++++++++++++++++----------------
6 files changed, 72 insertions(+), 31 deletions(-)
next reply other threads:[~2025-04-22 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 16:52 David Sterba [this message]
2025-04-22 20:54 ` [GIT PULL] Btrfs fixes for 6.15-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.1745339483.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.