On 10/27/20 4:46 PM, Roman Bolshakov wrote: > Thanks for raising the point about overlength/underlength. If you wish > we can add an extra check that fails DMA_TO_DEVICE && DATA with > residuals only for SBC devices but note that before the series, > underflow/overflow for WRITE didn't return GOOD status. The particular > patch only changes sense code to more meaningful from the former INVALID > FIELD IN CDB. > > Theoretically, it could be good to have a configurable switch how LIO > handles overflows/underflows for a LUN. Then it'd be possible to > configure desired behaviour on a per-LUN basis. But there should be a > clear need & demand for the feature to avoid maintenance of dead code. >>> An additional question is what behavior other operating systems than >> Linux expect? There are probably setups in which another operating >> system than Linux communicates with a LIO SCSI target? > > TBH I don't know any hosts that do SBC WRITE with residuals as normal > course of operation. They wouldn't be able to work with LIO because it > never returns GOOD status on WRITE with residuals. I can send an update > later if the series works fine with modern hosts (~1 month, after a few > cycles of system testing). Hi Roman, I'm not sure adding a new kernel switch is the best choice. That would be an additional parameter users have to know about and have to learn how to use. Bodo seems to be in favor of this patch series. Are there other people who want to share their opinion about this patch series? Thanks, Bart.
