btrfs: fsync changes, a bug fix and a couple improvements
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | btrfs: fix lost inode on log replay after mix of fsync, rename and inode evictionfs/ | +2 | 0 replies | |
| 2/3 | btrfs: eliminate some false positives when checking if inode was loggedfs/ | +16 | 0 replies | |
| 3/3 | btrfs: do not pin logs too early during renamesfs/ | +42 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] btrfs: fsync changes, a bug fix and a couple improvements
From: Filipe Manana <[email protected]>
The first patch in the series fixes a bug where a directory fsync, following by inode eviction, followed by renaming a file and syncing the log results in losing a file if a power failure happens and the log is replayed.
The remaining two changes are independent, and are about avoiding unnecessary work during operations that need to check or modify the log (renames, adding a hard link, unlinks) and making renames hold log commits for a shorter period.
Filipe Manana (3):
btrfs: fix lost inode on log replay after mix of fsync, rename and inode eviction
btrfs: eliminate some false positives when checking if inode was logged
btrfs: do not pin logs too early during renames
fs/btrfs/inode.c | 48 +++++++++++++++++++++++++++++++++++++++------ fs/btrfs/tree-log.c | 29 ++++++++++++++++----------- 2 files changed, 60 insertions(+), 17 deletions(-)
Signature · 1 line
2.28.0