From: Takashi Iwai <tiwai@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: "Christian König" <christian.koenig@amd.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swiotlb: Fix unexpected swiotlb_alloc_coherent() failures
Date: Tue, 10 Apr 2018 19:07:46 +0200 [thread overview]
Message-ID: <s5hzi2bat25.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180410170615.GA27589@lst.de>
On Tue, 10 Apr 2018 19:06:15 +0200,
Christoph Hellwig wrote:
>
> On Tue, Apr 10, 2018 at 07:05:13PM +0200, Takashi Iwai wrote:
> > The code refactoring by commit 0176adb00406 ("swiotlb: refactor
> > coherent buffer allocation") made swiotlb_alloc_buffer() almost always
> > failing due to a thinko: namely, the function evaluates the
> > dma_coherent_ok() call incorrectly and dealing as if it's invalid.
> > This ends up with weird errors like iwlwifi probe failure or amdgpu
> > screen flickering.
> >
> > This patch corrects the logic error.
>
> This looks ok, although even hitting this code is a bad sign. Do you
> know why the previous dma_direct_alloc didn't succeed?
That I have no idea, sorry. I just figured out the regression just
from the dmesg output of 4.16 kernel in bugzilla reports.
Could you take a look at the bugzilla reports there?
thanks,
Takashi
> > Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1088658
> > Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1088902
> > Fixes: 0176adb00406 ("swiotlb: refactor coherent buffer allocation")
> > Cc: <stable@vger.kernel.org> # v4.16+
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> > lib/swiotlb.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/swiotlb.c b/lib/swiotlb.c
> > index 47aeb04c1997..de7cc540450f 100644
> > --- a/lib/swiotlb.c
> > +++ b/lib/swiotlb.c
> > @@ -719,7 +719,7 @@ swiotlb_alloc_buffer(struct device *dev, size_t size, dma_addr_t *dma_handle,
> > goto out_warn;
> >
> > *dma_handle = __phys_to_dma(dev, phys_addr);
> > - if (dma_coherent_ok(dev, *dma_handle, size))
> > + if (!dma_coherent_ok(dev, *dma_handle, size))
> > goto out_unmap;
> >
> > memset(phys_to_virt(phys_addr), 0, size);
> > --
> > 2.16.3
> ---end quoted text---
>
next prev parent reply other threads:[~2018-04-10 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 17:05 [PATCH] swiotlb: Fix unexpected swiotlb_alloc_coherent() failures Takashi Iwai
2018-04-10 17:06 ` Christoph Hellwig
2018-04-10 17:07 ` Takashi Iwai [this message]
2018-04-10 17:50 ` Robin Murphy
2018-04-10 18:10 ` Christoph Hellwig
2018-04-11 7:28 ` Takashi Iwai
2018-04-12 6:02 ` Christoph Hellwig
2018-04-12 8:03 ` Takashi Iwai
2018-04-12 8:19 ` Takashi Iwai
2018-04-12 8:27 ` Takashi Iwai
2018-04-12 10:32 ` Robin Murphy
2018-04-15 8:43 ` Takashi Iwai
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=s5hzi2bat25.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=christian.koenig@amd.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/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