fuse: direct-io: don't dirty ITER_BVEC pages

When reading from a loop device backed by a fuse file it deadlocks on
lock_page().

This is because the page is already locked by the read() operation done on
the loop device.  In this case we don't want to either lock the page or
dirty it.

So do what fs/direct-io.c does: only dirty the page for ITER_IOVEC vectors.

Reported-by: Sheng Yang <[email protected]>
Fixes: aa4d86163e4e ("block: loop: switch to VFS ITER_BVEC")
Signed-off-by: Miklos Szeredi <[email protected]>
Cc: <[email protected]> # v4.1+
Reviewed-by: Sheng Yang <[email protected]>
Reviewed-by: Ashish Samant <[email protected]>
Tested-by: Sheng Yang <[email protected]>
Tested-by: Ashish Samant <[email protected]>

0 files changed, 0 insertions, 0 deletions