public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/2] btrfs: fix log replay not persisting a 0 i_size
@ 2026-02-17 18:27 fdmanana
  2026-02-17 18:27 ` [PATCH 1/2] btrfs: fix zero size inode with non-zero size after log replay fdmanana
  2026-02-17 18:27 ` [PATCH 2/2] btrfs: pass a btrfs inode to tree-log.c:fill_inode_item() fdmanana
  0 siblings, 2 replies; 3+ messages in thread
From: fdmanana @ 2026-02-17 18:27 UTC (permalink / raw)
  To: linux-btrfs

From: Filipe Manana <fdmanana@suse.com>

Fix an issue where if we fsync a file that got its size truncated to 0, we
may end up not getting an i_size of 0 after log replay if new names for the
file were also logged. Details in the change log of the first patch.

Filipe Manana (2):
  btrfs: fix zero size inode with non-zero size after log replay
  btrfs: pass a btrfs inode to tree-log.c:fill_inode_item()

 fs/btrfs/tree-log.c | 140 +++++++++++++++++++++++++++-----------------
 1 file changed, 85 insertions(+), 55 deletions(-)

-- 
2.47.2


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-02-17 18:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-17 18:27 [PATCH 0/2] btrfs: fix log replay not persisting a 0 i_size fdmanana
2026-02-17 18:27 ` [PATCH 1/2] btrfs: fix zero size inode with non-zero size after log replay fdmanana
2026-02-17 18:27 ` [PATCH 2/2] btrfs: pass a btrfs inode to tree-log.c:fill_inode_item() fdmanana

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox