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.19-rc6
Date: Sun, 18 Jan 2026 03:49:08 +0100 [thread overview]
Message-ID: <cover.1768703360.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes, thanks.
- with large folios in use, fix partial incorrect update of a reflinked
range
- fix potential deadlock in iget when lookup fails and eviction is
needed
- in send, validate inline extent type while detecting file holes
- fix memory leak after an error when creating a space info
- remove zone statistics from sysfs again, the output size limitations
make it unusable, we'll do it in another way in another release
- test fixes:
- return proper error codes from block remapping tests
- fix tree root leaks in qgroup tests after errors
----------------------------------------------------------------
The following changes since commit 2bb83bc42be6280d9bc363b8fbcd6fdab690d16d:
btrfs: show correct warning if can't read data reloc tree (2026-01-06 01:23:00 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.19-rc5-tag
for you to fetch changes up to 437cc6057e01d98ee124496f045ede36224af326:
btrfs: remove zoned statistics from sysfs (2026-01-14 22:08:04 +0100)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: release path before iget_failed() in btrfs_read_locked_inode()
btrfs: invalidate pages instead of truncate after reflinking
Jiasheng Jiang (1):
btrfs: fix memory leaks in create_space_info() error paths
Johannes Thumshirn (1):
btrfs: remove zoned statistics from sysfs
Naohiro Aota (1):
btrfs: tests: fix return 0 on rmap test failure
Qu Wenruo (2):
btrfs: send: check for inline extents in range_is_hole_in_parent()
btrfs: update the Kconfig string for CONFIG_BTRFS_EXPERIMENTAL
Zilin Guan (1):
btrfs: tests: fix root tree leak in btrfs_test_qgroups()
fs/btrfs/Kconfig | 6 ++++-
fs/btrfs/inode.c | 9 +++++++
fs/btrfs/reflink.c | 23 +++++++++--------
fs/btrfs/send.c | 2 ++
fs/btrfs/space-info.c | 8 ++++--
fs/btrfs/sysfs.c | 52 ---------------------------------------
fs/btrfs/tests/extent-map-tests.c | 3 +++
fs/btrfs/tests/qgroup-tests.c | 6 ++---
8 files changed, 41 insertions(+), 68 deletions(-)
next reply other threads:[~2026-01-18 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 2:49 David Sterba [this message]
2026-01-19 13:53 ` [GIT PULL] Btrfs fixes for 6.19-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.1768703360.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.