On 2013-05-14, at 0:25, Daniel Phillips <daniel.raymond.phillips@xxxxxxxxx> wrote: > Interesting, Andreas. We don't do anything as heavyweight as > allocating an inode in this path, just mark the inode dirty (which > puts it on a list) and set a bit in the inode flags. The new inode allocation is only needed for the truncate-to-zero case. If the inode is being deleted it is used directly. Sorry for confusion, it has been a long time since I looked at that code. Cheers, Andreas-- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
