From: Christoph Hellwig <hch@infradead.org>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
sachinp <sachinp@linux.vnet.ibm.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
jcmvbkbc@gmail.com, linux-next <linux-next@vger.kernel.org>,
Oliver <oohall@gmail.com>,
"aneesh.kumar" <aneesh.kumar@linux.vnet.ibm.com>,
Brian King <brking@linux.vnet.ibm.com>,
manvanth <manvanth@linux.vnet.ibm.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver
Date: Thu, 9 Jan 2020 06:22:18 -0800 [thread overview]
Message-ID: <20200109142218.GA16477@infradead.org> (raw)
In-Reply-To: <1578560245.30409.0.camel@abdul.in.ibm.com>
On Thu, Jan 09, 2020 at 02:27:25PM +0530, Abdul Haleem wrote:
> + CC Christoph Hellwig
The only thing this commit changed for the dma coherent case (which
ppc64 uses) is that we now look up the page to free by the DMA address
instead of the virtual address passed in. Which suggests this call
stack passes in a broken dma address. I suspect we somehow managed
to disable the ppc iommu bypass mode after allocating memory, which
would cause symptoms like this, and thus the commit is just exposing
a pre-existing problem.
next prev parent reply other threads:[~2020-01-09 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 13:18 [linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver Abdul Haleem
2020-01-09 8:57 ` Abdul Haleem
2020-01-09 14:22 ` Christoph Hellwig [this message]
2020-01-14 5:47 ` Abdul Haleem
2020-01-16 6:42 ` Michael Ellerman
2020-01-16 17:44 ` Christoph Hellwig
2020-01-17 12:51 ` Abdul Haleem
2020-02-25 6:20 ` Abdul Haleem
2020-02-25 6:53 ` Sreekanth Reddy
2020-03-20 9:59 ` Abdul Haleem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200109142218.GA16477@infradead.org \
--to=hch@infradead.org \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manvanth@linux.vnet.ibm.com \
--cc=oohall@gmail.com \
--cc=sachinp@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).