first step toward the new truncate sequence
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 16 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | sort out blockdev_direct_IO variantsfs/ fs/ fs/ +12 more | +141 | 3 replies | |
| 2/6 | get rid of nobh_write_begin_newtruncfs/ fs/ fs/ +1 more | +17 | 0 replies | |
| 3/6 | get rid of cont_write_begin_newtruncfs/ fs/ fs/ +6 more | +62 | 0 replies | |
| 4/6 | clean up write_begin usage for directories in pagecachefs/ fs/ fs/ +10 more | +57 | 0 replies | |
| 5/6 | introduce __block_write_beginfs/ fs/ fs/ +7 more | +38 | 4 replies | |
| 6/6 | get rid of block_write_begin_newtruncfs/ fs/ fs/ +10 more | +103 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] first step toward the new truncate sequence
This series is something that I see as the first major step towards a broad switch to the new truncate sequence. The patches get rid of the _newtrunc variant of blockdev_direct_IO & friends and *_write_begin, and clean up some bits in that area that make the switch easier. After this we have all vmtruncate instances except for inode_setattr in filesystem code. A second series to deal with ->setattr will follow and after that we can easily switch over one filesystem after another.
I think this is still 2.6.34 material as it will make the fs switches a lot easier and avoid introducing the _newtrunc variants for one kernel release.