Skip to content

btrfs: fixes for missing error reporting when attaching to a transaction

[email protected] linux-btrfs 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 3 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2btrfs: check if the transaction was aborted at btrfs_wait_for_commit()fs/btrfs/transaction.c+1 -01 reply
2/2btrfs: check for commit error at btrfs_attach_transaction_barrier()fs/btrfs/transaction.c+7 -21 reply

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchQu Wenruo
1/2R-b
2/2R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] btrfs: fixes for missing error reporting when attaching to a transaction

From: Filipe Manana <[email protected]>

These fix missing error checks and returns when attaching to a transaction in barrier mode, and waiting for a transaction to commit and finish. These can make things like an fsync that fallbacks to a transaction commit to report success to user space when a transaction was aborted and the inode changes were therefore not persisted. More details on the change logs.

Filipe Manana (2):
btrfs: check if the transaction was aborted at btrfs_wait_for_commit()
btrfs: check for commit error at btrfs_attach_transaction_barrier()

 fs/btrfs/transaction.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)
Signature · 1 line
2.34.1