On Thu, Jun 03, 2010 at 12:58:22PM +0200, Miklos Szeredi wrote: > (In fact I think it would be cleanest if truncate/ftruncate was a > separate operation from setattr on all levels, but that's a different > story.) It might be. Let's finish off the current transition after which we should have all truncate code in a clean if (valid & ATTR_SIZE) inside the setattr method. We can think about re-introducing a proper truncate method after that, although I'm not sure how much duplication the timestamp and mode updates will mean. The upside of it is that many filesystems could remove the setattr method after this, though. -- 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
