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 7.0-rc6
Date: Sat, 28 Mar 2026 22:18:56 +0100 [thread overview]
Message-ID: <cover.1774730316.git.dsterba@suse.com> (raw)
Hi,
please pull a few more fixes. There's one that stands out in size as it
fixes an edge case in fsync. Thanks.
- fix issue on fsync where file with zero size appears as a non-zero
after log replay
- in zlib compression, handle a crash when data alignment causes folio
reference issues
- fix possible crash with enabled tracepoints on a overlayfs mount
- handle device stats update error
- on zoned filesystems, fix kobject leak on sub-block groups
- fix super block offset in an error message in validation
----------------------------------------------------------------
The following changes since commit b17b79ff896305fd74980a5f72afec370ee88ca4:
btrfs: reject root items with drop_progress and zero drop_level (2026-03-17 11:43:08 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-7.0-rc5-tag
for you to fetch changes up to 1c37d896b12dfd0d4c96e310b0033c6676933917:
btrfs: fix lost error when running device stats on multiple devices fs (2026-03-23 20:12:12 +0100)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: fix zero size inode with non-zero size after log replay
btrfs: fix lost error when running device stats on multiple devices fs
Goldwyn Rodrigues (1):
btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file()
Mark Harmstone (1):
btrfs: fix super block offset in error message in btrfs_validate_super()
Qu Wenruo (1):
btrfs: zlib: handle page aligned compressed size correctly
Shin'ichiro Kawasaki (1):
btrfs: fix leak of kobject name for sub-group space_info
fs/btrfs/block-group.c | 2 +-
fs/btrfs/disk-io.c | 4 +-
fs/btrfs/tree-log.c | 98 +++++++++++++++++++++++++++++---------------
fs/btrfs/volumes.c | 5 ++-
fs/btrfs/zlib.c | 4 +-
include/trace/events/btrfs.h | 11 +++--
6 files changed, 81 insertions(+), 43 deletions(-)
next reply other threads:[~2026-03-28 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 21:18 David Sterba [this message]
2026-03-29 16:42 ` [GIT PULL] Btrfs fixes for 7.0-rc6 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.1774730316.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