Skip to content

first step toward the new truncate sequence

Christoph Hellwig linux-fsdevel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 16 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6sort out blockdev_direct_IO variantsfs/block_dev.c fs/direct-io.c fs/ext2/inode.c +12 more+141 -1153 replies
2/6get rid of nobh_write_begin_newtruncfs/buffer.c fs/ext2/inode.c fs/jfs/inode.c +1 more+17 -460 replies
3/6get rid of cont_write_begin_newtruncfs/adfs/inode.c fs/affs/file.c fs/buffer.c +6 more+62 -300 replies
4/6clean up write_begin usage for directories in pagecachefs/ext2/dir.c fs/ext2/ext2.h fs/ext2/inode.c +10 more+57 -1070 replies
5/6introduce __block_write_beginfs/buffer.c fs/ext2/dir.c fs/ext3/inode.c +7 more+38 -644 replies
6/6get rid of block_write_begin_newtruncfs/bfs/file.c fs/block_dev.c fs/buffer.c +10 more+103 -910 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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.