[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1492096576.3298.2.camel@sandisk.com>
Date: Thu, 13 Apr 2017 15:16:19 +0000
From: Bart Van Assche <Bart.VanAssche@...disk.com>
To: "jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
"jthumshirn@...e.de" <jthumshirn@...e.de>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>
CC: "hch@....de" <hch@....de>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hare@...e.de" <hare@...e.de>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH v2] scsi: return correct blkprep status code in case
scsi_init_io() fails.
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 ('scsi: don't BUG_ON()
> empty DMA transfers') we return the wrong error value from scsi_prep_fn()
> back to the block layer.
Reviewed-by: Bart Van Assche <bart.vanassche@...disk.com>
Powered by blists - more mailing lists