[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1bMRNhmq41/y3Jb@infradead.org>
Date: Mon, 24 Oct 2022 10:32:52 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Andrew Cooper <Andrew.Cooper3@...rix.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Juergen Gross <jgross@...e.com>,
"jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
Sreekanth Reddy <sreekanth.reddy@...adcom.com>,
Bart Van Assche <bvanassche@....org>,
Salvatore Bonaccorso <carnil@...ian.org>,
"sathya.prakash@...adcom.com" <sathya.prakash@...adcom.com>,
"suganath-prabu.subramani@...adcom.com"
<suganath-prabu.subramani@...adcom.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"MPT-FusionLinux.pdl@...adcom.com" <MPT-FusionLinux.pdl@...adcom.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
"adi@...egisch.at" <adi@...egisch.at>
Subject: Re: Report in downstream Debian: mpt3sas broken with xen dom0 with
update to 5.10.149 in 5.10.y.
On Mon, Oct 24, 2022 at 05:28:05PM +0000, Andrew Cooper wrote:
> I don't know exactly how this translates to Linux internals, but most
> devices are fine and it's routinely the mpt2/3sas drivers which
> encounter problems. It would be lovely if we could get to the bottom of
> this for once and for all.
So to summarize my two mails: I think te use of dma_get_required_mask
in mpt3sas is wrong, and the dma_get_required_mask return value from
xen-swiotlb is also wrong. Fixing either one should fix this problem,
and I think we should fix both.
Powered by blists - more mailing lists