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-rc2
Date: Mon, 15 Dec 2025 20:50:02 +0100 [thread overview]
Message-ID: <cover.1765827039.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes. Thanks.
- fix missing btrfs_path release after printing a relocation error
message
- fix extent changeset leak on mmap write after failure to reserve
metadata
- fix fs devices list structure freeing, it could be potentially leaked
under some circumstances
- tree log fixes:
- fix incremental directory logging where inodes for new dentries were
incorrectly skipped
- don't log conflicting inode if it's a directory moved in the current
transaction
- regression fixes:
- fix incorrect btrfs_path freeing when it's auto-cleaned
- revert commit simplifying preallocation of temporary structures in
qgroup functions, some cases were not handled properly
----------------------------------------------------------------
The following changes since commit 9e0e6577b3e5e5cf7c1acd178eb648e8f830ba17:
btrfs: remove unnecessary inode key in btrfs_log_all_parents() (2025-11-25 01:53:33 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.19-rc1-tag
for you to fetch changes up to 37343524f000d2a64359867d7024a73233d3b438:
btrfs: fix changeset leak on mmap write after failure to reserve metadata (2025-12-12 16:33:18 +0100)
----------------------------------------------------------------
Dan Carpenter (1):
btrfs: tests: fix double btrfs_path free in remove_extent_ref()
Deepanshu Kartikey (1):
btrfs: fix memory leak of fs_devices in degraded seed device path
Filipe Manana (3):
btrfs: don't log conflicting inode if it's a dir moved in the current transaction
btrfs: do not skip logging new dentries when logging a new name
btrfs: fix changeset leak on mmap write after failure to reserve metadata
Qu Wenruo (2):
Revert "btrfs: add ASSERTs on prealloc in qgroup functions"
btrfs: fix a potential path leak in print_data_reloc_error()
fs/btrfs/file.c | 3 ++-
fs/btrfs/inode.c | 1 +
fs/btrfs/qgroup.c | 27 ++++---------------------
fs/btrfs/tests/qgroup-tests.c | 1 -
fs/btrfs/tree-log.c | 46 +++++++++++++++++++++++++++++++++++--------
fs/btrfs/volumes.c | 1 +
6 files changed, 46 insertions(+), 33 deletions(-)
next reply other threads:[~2025-12-15 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 19:50 David Sterba [this message]
2025-12-16 8:04 ` [GIT PULL] Btrfs fixes for 6.19-rc2 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.1765827039.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.