diff options
| author | Christoph Hellwig <hch@lst.de> | 2016-03-03 22:43:45 +0100 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2016-03-03 22:43:45 +0100 |
| commit | f21018427cb007a0894c36ad702990ab639cbbb4 (patch) | |
| tree | 88eff3b50155c51a210c61b0805f5a9c0daa9a14 /block | |
| parent | nvme: fix max_segments integer truncation (diff) | |
| download | linux-f21018427cb007a0894c36ad702990ab639cbbb4.tar.xz linux-f21018427cb007a0894c36ad702990ab639cbbb4.zip | |
block: fix blk_rq_get_max_sectors for driver private requests
Driver private request types should not get the artifical cap for the
FS requests. This is important to use the full device capabilities
for internal command or NVMe pass through commands.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reported-by: Jeff Lien <Jeff.Lien@hgst.com>
Tested-by: Jeff Lien <Jeff.Lien@hgst.com>
Reviewed-by: Keith Busch <keith.busch@intel.com>
Updated by me to use an explicit check for the one command type that
does support extended checking, instead of relying on the ordering
of the enum command values - as suggested by Keith.
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions