ocfs2: fix some inconsistency problems caused by jbd2_journal_restart()
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ocfs2: extend transaction for ocfs2_remove_rightmost_path and ocfs2_update_edge_lengths before to avoid inconsistency between inode and etfs/ | +54 | 0 replies | |
| 2/3 | ocfs2: do not set fs read-only if rec[0] is empty while committing truncatefs/ | +38 | 0 replies | |
| 3/3 | extend enough credits for freeing one truncate record while replaying truncate recordsfs/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Ocfs2-devel] [PATCH 0/3] ocfs2: fix some inconsistency problems caused by jbd2_journal_restart()
I found that function jbd2_journal_restart() is called some places in ocfs2 without keeping things consistently before. However, jbd2_journal_restart() may commit the handle's transaction and restart another one. If the first transaction is committed successfully while another not, it may cause filesystem inconsistency or read only. This is an effort to fix this kind of problems.
Any comments are appreciated, thanks!