Re: [PATCH v2] scsi: return correct blkprep status code in case scsi_init_io() fails.

2017-04-13 Thread Martin K. Petersen
Johannes Thumshirn writes: > When instrumenting the SCSI layer to run into the > !blk_rq_nr_phys_segments(rq) case the following warning emitted from > the block layer: Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v2] scsi: return correct blkprep status code in case scsi_init_io() fails.

2017-04-13 Thread Bart Van Assche
On Wed, 2017-04-12 at 09:21 +0200, Johannes Thumshirn wrote: > When instrumenting the SCSI layer to run into the > !blk_rq_nr_phys_segments(rq) case the following warning emitted from the > block layer: > > blk_peek_request: bad return=-22 > > This happens because since commit fd3fc0b4d730

Re: [PATCH v2] scsi: return correct blkprep status code in case scsi_init_io() fails.

2017-04-12 Thread Hannes Reinecke
On 04/12/2017 09:21 AM, Johannes Thumshirn wrote: > When instrumenting the SCSI layer to run into the > !blk_rq_nr_phys_segments(rq) case the following warning emitted from the > block layer: > > blk_peek_request: bad return=-22 > > This happens because since commit fd3fc0b4d730 ('scsi: don't

[PATCH v2] scsi: return correct blkprep status code in case scsi_init_io() fails.

2017-04-12 Thread Johannes Thumshirn
When instrumenting the SCSI layer to run into the !blk_rq_nr_phys_segments(rq) case the following warning emitted from the block layer: blk_peek_request: bad return=-22 This happens because since commit fd3fc0b4d730 ('scsi: don't BUG_ON() empty DMA transfers') we return the wrong error value