commit | ef5f5a3a63f8b7c472f30484c520265aba6ef162 | [log] [tgz] |
---|---|---|
author | Jens Axboe <axboe@kernel.dk> | Wed Dec 12 08:34:42 2012 +0100 |
committer | Jens Axboe <axboe@kernel.dk> | Wed Dec 12 08:34:42 2012 +0100 |
tree | c19c000addbf1012b12daa3e147484c925a7a15a | |
parent | e6c4d732fc99070091367d0ce41fe2cf1ddd1dc9 [diff] |
file: unify ->file_data and ->file_pos The only real use case of ->file_pos was by the sync engine to avoid an lseek() if the offset was already correct. The e4defrag, falloc, and fusion-aw engine also set ->file_pos, but that looks like a case of copy-paste, since they don't actually use it. Signed-off-by: Jens Axboe <axboe@kernel.dk>