Excerpts from Christoph Hellwig's message of 2011-04-15 15:24:12 -0400: > Sorry, but this is too ugly to live. If the reason for this really is > good enough we'll just need to push the filemap_write_and_wait_range > and i_mutex locking into every ->fsync instance. > Which part is too ugly to live? The special op? New parameters? The unconditional taking of i_mutex hurts a lot, especially on directory fsyncs, so I'd love to get rid of it. -chris -- 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
