Slightly how START_SYNC and WAIT_SYNC work
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | btrfs: sink wait_for_unblock parameter to async commitfs/ fs/ fs/ | +4 | 1 reply | |
| 2/4 | btrfs: inline wait_current_trans_commit_start in its callerfs/ | +7 | 1 reply | |
| 3/4 | btrfs: replace async commit by pending actionsfs/ fs/ fs/ | +5 | 0 replies | |
| 4/4 | btrfs: remove fs_info::transaction_blocked_waitfs/ fs/ fs/ +1 more | +4 | 0 replies |
Reviews trailers per patch
2 of 4 patches have a Reviewed-by or Acked-by.
| Patch | Anand Jain |
|---|---|
| 1/4 | R-b |
| 2/4 | R-b |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] Slightly how START_SYNC and WAIT_SYNC work
The async transaction commit ioctl has a subtle semantics that used to work for ceph. We need more straightforward semantics in progs (eg. when waiting for commit after subvolume deletion) and otherwise the async commit does a few annoying things.
Long explanation is in patch 3. I hope it works, but somebody please double check. It's a minor change in the commit logic, but merely removing some waiting, no other changes in state transitions.
David Sterba (4):
btrfs: sink wait_for_unblock parameter to async commit
btrfs: inline wait_current_trans_commit_start in its caller
btrfs: replace async commit by pending actions
btrfs: remove fs_info::transaction_blocked_wait
fs/btrfs/ctree.h | 1 - fs/btrfs/disk-io.c | 5 +- fs/btrfs/ioctl.c | 12 ++--- fs/btrfs/super.c | 1 - fs/btrfs/transaction.c | 103 +---------------------------------------- fs/btrfs/transaction.h | 2 - 6 files changed, 9 insertions(+), 115 deletions(-)
Signature · 1 line
2.31.1