ext3 and ext4 heave inherited the nobh option from ext2, but the implementation is rather interesting. Except for the usual option parsing / display it's only respected in ext3_writeback_writepage/ext4_writepage and the truncate_page implementation. Given that we don't take any more than usual care to not create buffers heads during read this is not going to effect a whole lot. Is there a good reason to keep these options and the associated code complexity? I'd be rather surprised if it gets any sufficient testing.. -- 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
