* [GIT PULL] Btrfs fixes for 6.18-rc5
@ 2025-11-04 4:57 David Sterba
2025-11-04 5:45 ` pr-tracker-bot
0 siblings, 1 reply; 2+ messages in thread
From: David Sterba @ 2025-11-04 4:57 UTC (permalink / raw)
To: torvalds; +Cc: David Sterba, linux-btrfs, linux-kernel
Hi,
please pull a few more short fixes. Thanks.
- fix memory leak in qgroup relation ioctl when qgroup levels are
invalid
- don't write back dirty metadata on filesystem with errors
- properly log renamed links
- properly mark prealloc extent range beyond inode size as dirty
(when no-noles is not enabled)
----------------------------------------------------------------
The following changes since commit ada7d45b568abe4f1fd9c53d66e05fbea300674b:
btrfs: ref-verify: fix IS_ERR() vs NULL check in btrfs_build_ref_tree() (2025-10-22 09:40:07 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.18-rc4-tag
for you to fetch changes up to 3b1a4a59a2086badab391687a6a0b86e03048393:
btrfs: mark dirty extent range for out of bound prealloc extents (2025-10-30 19:18:18 +0100)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name
Qu Wenruo (1):
btrfs: ensure no dirty metadata is written back for an fs with errors
Shardul Bankar (1):
btrfs: fix memory leak of qgroup_list in btrfs_add_qgroup_relation
austinchang (1):
btrfs: mark dirty extent range for out of bound prealloc extents
fs/btrfs/extent_io.c | 8 ++++++++
fs/btrfs/file.c | 10 ++++++++++
fs/btrfs/inode.c | 1 -
fs/btrfs/qgroup.c | 4 +++-
fs/btrfs/tree-log.c | 3 +++
5 files changed, 24 insertions(+), 2 deletions(-)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-11-04 5:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-11-04 4:57 [GIT PULL] Btrfs fixes for 6.18-rc5 David Sterba
2025-11-04 5:45 ` pr-tracker-bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox