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.17-rc6
Date: Thu, 11 Sep 2025 07:37:37 +0200 [thread overview]
Message-ID: <cover.1757568026.git.dsterba@suse.com> (raw)
Hi,
please pull a few more fixes for btrfs. Thanks.
- fix delayed inode tracking in xarray, eviction can race with insertion
and leave behind a disconnected inode
- on systems with large page (64K) and small block size (4K) fix
compression read that can return partially filled folio
- slightly relax compression option format for backward compatibility,
allow to specify level for LZO although there's only one
- fix simple quota accounting of compressed extents
- validate minimum device size in 'device add'
- update maintainers' entry
----------------------------------------------------------------
The following changes since commit 986bf6ed44dff7fbae7b43a0882757ee7f5ba21b:
btrfs: avoid load/store tearing races when checking if an inode was logged (2025-08-22 00:58:55 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc5-tag
for you to fetch changes up to 3d1267475b94b3df7a61e4ea6788c7c5d9e473c4:
btrfs: don't allow adding block device of less than 1 MB (2025-09-05 19:52:10 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: fix squota compressed stats leak
Calvin Owens (1):
btrfs: accept and ignore compression level for lzo
Josef Bacik (1):
MAINTAINERS: update btrfs entry
Mark Harmstone (1):
btrfs: don't allow adding block device of less than 1 MB
Omar Sandoval (1):
btrfs: fix subvolume deletion lockup caused by inodes xarray race
Qu Wenruo (1):
btrfs: fix corruption reading compressed range when block size is smaller than page size
MAINTAINERS | 1 -
fs/btrfs/extent_io.c | 40 ++++++++++++++++++++++++++++++----------
fs/btrfs/inode.c | 12 +++++++++++-
fs/btrfs/qgroup.c | 6 ++++--
fs/btrfs/super.c | 9 ++++++---
fs/btrfs/volumes.c | 5 +++++
6 files changed, 56 insertions(+), 17 deletions(-)
next reply other threads:[~2025-09-11 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 5:37 David Sterba [this message]
2025-09-11 15:53 ` [GIT PULL] Btrfs fixes for 6.17-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.1757568026.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