diff options
author | Jens Axboe <axboe@kernel.dk> | 2021-09-10 11:18:36 -0600 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2021-09-14 08:12:18 -0600 |
commit | 8fb0f47a9d7acf620d0fd97831b69da9bc5e22ed (patch) | |
tree | 89e9ff5375b25a40b66986e284fdf7a7592ed3b1 /fs | |
parent | d6c338a741295c04ed84679153448b2fffd2c9cf (diff) | |
download | linux-8fb0f47a9d7acf620d0fd97831b69da9bc5e22ed.tar.bz2 |
iov_iter: add helper to save iov_iter state
In an ideal world, when someone is passed an iov_iter and returns X bytes,
then X bytes would have been consumed/advanced from the iov_iter. But we
have use cases that always consume the entire iterator, a few examples
of that are iomap and bdev O_DIRECT. This means we cannot rely on the
state of the iov_iter once we've called ->read_iter() or ->write_iter().
This would be easier if we didn't always have to deal with truncate of
the iov_iter, as rewinding would be trivial without that. We recently
added a commit to track the truncate state, but that grew the iov_iter
by 8 bytes and wasn't the best solution.
Implement a helper to save enough of the iov_iter state to sanely restore
it after we've called the read/write iterator helpers. This currently
only works for IOVEC/BVEC/KVEC as that's all we need, support for other
iterator types are left as an exercise for the reader.
Link: https://lore.kernel.org/linux-fsdevel/CAHk-=wiacKV4Gh-MYjteU0LwNBSGpWrK-Ov25HdqB1ewinrFPg@mail.gmail.com/
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions