linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-mm@kvack.org,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	rientjes@google.com, Christoph Hellwig <hch@lst.de>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [BUG] XHCI getting ZONE_DMA32 memory > than its bus_dma_limit
Date: Thu, 2 Jul 2020 12:49:14 -0500	[thread overview]
Message-ID: <34619bdf-6527-ae82-7e4d-e2ea7c67ed56@arm.com> (raw)

Hi,

Using 5.8rc3:

The rpi4 has a 3G dev->bus_dma_limit on its XHCI controller. With a usb3 
hub, plus a few devices plugged in, randomly devices will fail 
operations. This appears to because xhci_alloc_container_ctx() is 
getting buffers > 3G via dma_pool_zalloc().

Tracking that down, it seems to be caused by dma_alloc_from_pool() using 
dev_to_pool()->dma_direct_optimal_gfp_mask() to "optimistically" select 
the atomic_pool_dma32 but then failing to verify that the allocations in 
the pool are less than the dev bus_dma_limit.

Thanks,


             reply	other threads:[~2020-07-02 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 17:49 Jeremy Linton [this message]
2020-07-03 14:53 ` [BUG] XHCI getting ZONE_DMA32 memory > than its bus_dma_limit Nicolas Saenz Julienne
2020-07-03 17:42   ` Robin Murphy
2020-07-05 23:41     ` David Rientjes
2020-07-06 14:09       ` Nicolas Saenz Julienne
2020-07-07  6:55         ` Christoph Hellwig

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=34619bdf-6527-ae82-7e4d-e2ea7c67ed56@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=hch@lst.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=rientjes@google.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).