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

2017-04-12 Thread Johannes Thumshirn
On Tue, Apr 11, 2017 at 06:43:22PM +, Bart Van Assche wrote: > On Tue, 2017-04-11 at 09:46 +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: > > > >

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

2017-04-11 Thread Bart Van Assche
On Tue, 2017-04-11 at 09:46 +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

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

2017-04-11 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