[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1756838388.git.dsterba@suse.com>
Date: Tue, 2 Sep 2025 20:44:31 +0200
From: David Sterba <dsterba@...e.com>
To: torvalds@...ux-foundation.org
Cc: David Sterba <dsterba@...e.com>,
linux-btrfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.17-rc5
Hi,
please pull a few inode logging fixes in tree-log. Thanks.
- fix a few races related to inode link count
- fix inode leak on failure to add link to inode
- move transaction aborts closer to where they happen
----------------------------------------------------------------
The following changes since commit 74857fdc5dd2cdcdeb6e99bdf26976fd9299d2bb:
btrfs: fix printing of mount info messages for NODATACOW/NODATASUM (2025-08-13 14:08:58 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc4-tag
for you to fetch changes up to 986bf6ed44dff7fbae7b43a0882757ee7f5ba21b:
btrfs: avoid load/store tearing races when checking if an inode was logged (2025-08-22 00:58:55 +0200)
----------------------------------------------------------------
Filipe Manana (6):
btrfs: abort transaction on failure to add link to inode
btrfs: fix inode leak on failure to add link to inode
btrfs: simplify error handling logic for btrfs_link()
btrfs: fix race between logging inode and checking if it was logged before
btrfs: fix race between setting last_dir_index_offset and inode logging
btrfs: avoid load/store tearing races when checking if an inode was logged
fs/btrfs/btrfs_inode.h | 2 +-
fs/btrfs/inode.c | 50 ++++++++++++++++----------------
fs/btrfs/tree-log.c | 78 ++++++++++++++++++++++++++++++++++----------------
3 files changed, 79 insertions(+), 51 deletions(-)
Powered by blists - more mailing lists