Fix fsync bug in ext3 and ext4
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ext3: Wait for proper transaction commit on fsyncfs/ fs/ include/ | +58 | 0 replies | |
| 2/4 | ext4: Avoid issuing barriers on error recovery pathfs/ | +3 | 0 replies | |
| 3/4 | ext4: Fix error handling ext4_ind_get_blocksfs/ | +1 | 0 replies | |
| 4/4 | ext4: Wait for proper transaction commit on fsyncfs/ fs/ fs/ +1 more | +63 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Fix fsync bug in ext3 and ext4
Hi,
the patch series below fixes the problem ext3 and ext4 has that we
rely on inode dirty bits for correct fsync. This has two problems:
a) ext3 and ext4 often does not set them (as they call ext?_mark_inode_dirty) and thus only quota code sets the dirty bit as a sideeffect.
b) pdflush can come in and clear the dirty bit any time (thanks to Chris for pointing out this).
The second and third patch in the series are just minor bug fixes to ext4.
I did some basic testing to verify that the code does what I'd expect it to do but an extra pair of eyes checking the new code would be helpful...
Honza