block: handle the null_mapped flag correctly in blk_rq_map_user_iov
authorChristoph Hellwig <hch@lst.de>
Wed, 11 Feb 2015 13:07:49 +0000 (14:07 +0100)
committerJens Axboe <axboe@fb.com>
Wed, 11 Feb 2015 18:24:12 +0000 (11:24 -0700)
commita0763b27bf24f028d8b049ad856b2ee031fb475d
tree7fba607dd8e679b6ee787b0c5257d7461c1bd8f5
parent564e559f2baf6a868768d0cac286980b3cfd6e30
block: handle the null_mapped flag correctly in blk_rq_map_user_iov

The tape drivers (and the sg driver in a special case that doesn't matter
here) use the null_mapped flag to tell blk_rq_map_user to not copy around
any data into or out of the bounce buffers.  blk_rq_map_user_iov never
got that treatment, which didn't matter until I refactored blk_rq_map_user
to be implemented in terms of blk_rq_map_user_iov.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Fixes: ddad8dd0a162 ("block: use blk_rq_map_user_iov to implement blk_rq_map_user")
Signed-off-by: Jens Axboe <axboe@fb.com>
block/blk-map.c