summaryrefslogtreecommitdiff
path: root/mm/highmem.c
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2023-08-28 18:47:31 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2023-10-27 20:14:11 -0400
commit1939316bf988f3e49a07d9c4dd6f660bf4daa53d (patch)
tree41ba99310df374f9125e15ee15f2a8e08dec6dd0 /mm/highmem.c
parent1f36cd05e0081f2c75769a551d584c4ffb2a5660 (diff)
io_uring: kiocb_done() should *not* trust ->ki_pos if ->{read,write}_iter() failed
->ki_pos value is unreliable in such cases. For an obvious example, consider O_DSYNC write - we feed the data to page cache and start IO, then we make sure it's completed. Update of ->ki_pos is dealt with by the first part; failure in the second ends up with negative value returned _and_ ->ki_pos left advanced as if sync had been successful. In the same situation write(2) does not advance the file position at all. Reviewed-by: Christian Brauner <brauner@kernel.org> Reviewed-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'mm/highmem.c')
0 files changed, 0 insertions, 0 deletions