The FIBMAP ioctl requires CAP_SYS_RAWIO, but FIEMAP doesn't. Why's that? Is it that there is no backwards-compatible way to introduce locking on the bmap path? (Sorting file access based on the first block number of the file really improves performance, even compared to inode number sorting, that's why I'm asking.) -- 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
