Careful here. What do all these errors from the low-level code mean here? I think we need to clearly standardize on what we actually return from ->map_sg and possibly document what the callers expect and can do, and enforce that only those error are reported.
- [PATCH v1 00/16] .map_sg() error cleanup Logan Gunthorpe
- [PATCH v1 01/16] dma-mapping: Allow map_sg() ops to... Logan Gunthorpe
- Re: [PATCH v1 01/16] dma-mapping: Allow map_sg(... Christoph Hellwig
- [PATCH v1 02/16] dma-direct: Return appropriate err... Logan Gunthorpe
- [PATCH v1 03/16] iommu: Return full error code from... Logan Gunthorpe
- [PATCH v1 04/16] dma-iommu: Return error code from ... Logan Gunthorpe
- Re: [PATCH v1 04/16] dma-iommu: Return error co... Christoph Hellwig
- [PATCH v1 13/16] xen: swiotlb: return error code fr... Logan Gunthorpe
- Re: [PATCH v1 13/16] xen: swiotlb: return error... Boris Ostrovsky
- [PATCH v1 15/16] dma-mapping: return error code fro... Logan Gunthorpe
- [PATCH v1 11/16] sparc/iommu: return error codes fr... Logan Gunthorpe
- [PATCH v1 16/16] dma-mapping: Disallow .map_sg oper... Logan Gunthorpe
- Re: [PATCH v1 16/16] dma-mapping: Disallow .map... Christoph Hellwig
- Re: [PATCH v1 16/16] dma-mapping: Disallow ... Robin Murphy
- Re: [PATCH v1 16/16] dma-mapping: Disallow ... Logan Gunthorpe
- [PATCH v1 10/16] s390/pci: return error code from s... Logan Gunthorpe
- Re: [PATCH v1 10/16] s390/pci: return error cod... Niklas Schnelle