All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215890] Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory
Date: Fri, 13 May 2022 10:37:38 +0000	[thread overview]
Message-ID: <bug-215890-208809-pejxoC7N5j@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215890-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215890

--- Comment #9 from Christoph Hellwig (hch@lst.de) ---
On Fri, May 13, 2022 at 10:24:34AM +0200, Thorsten Leemhuis wrote:
> On 04.05.22 10:42, Thorsten Leemhuis wrote:
> > 
> > Linux-Input developers, do you have any idea what might be causing the
> > problem outline below? It's a post 5.17 regression in mainline that was
> > reported to bugzilla.kernel.org about a week ago, but didn't even get a
> > single reply. Might be some other subsystem that is causing it, not sure.
> > 
> > On 27.04.22 00:42, bugzilla-daemon@kernel.org wrote:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=215890
> 
> FYI, the reporter bisected this regression down to f5ff79fddf0e
> ("dma-mapping: remove CONFIG_DMA_REMAP"). CCing Christoph, who authored
> that change (I wonder if it just exposed an existing bug, but well,
> that's up for you to discuss).
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
> 
> #regzbot introduced: f5ff79fddf0efecca538046b5cc20fb3ded2

Well, this just uncovered an existing bug in the driver.  You can not
just dma map memory returned from dma_alloc_coherent, and this driver
would already get vmalloc memory on arm/arm64 platforms anyway, we
now just do the same on x86 as well.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-05-13 10:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 22:42 [Bug 215890] New: Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory bugzilla-daemon
2022-05-02 14:19 ` [Bug 215890] " bugzilla-daemon
2022-05-04  8:42 ` [Bug 215890] New: " Thorsten Leemhuis
2022-05-13  8:24   ` Thorsten Leemhuis
2022-05-13 10:37     ` Christoph Hellwig
2022-05-13 10:47       ` Christoph Hellwig
2022-05-20  5:38   ` [Bug 215890] New: Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory #forregzbot Thorsten Leemhuis
2022-05-04  8:42 ` [Bug 215890] Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory bugzilla-daemon
2022-05-09  0:50 ` bugzilla-daemon
2022-05-10  8:48 ` bugzilla-daemon
2022-05-10 20:50 ` bugzilla-daemon
2022-05-11  5:44   ` Greg KH
2022-05-11  5:44 ` bugzilla-daemon
2022-05-12 16:36 ` bugzilla-daemon
2022-05-13  8:24 ` bugzilla-daemon
2022-05-13 10:37 ` bugzilla-daemon [this message]
2022-05-13 10:47 ` bugzilla-daemon
2022-05-13 13:21 ` bugzilla-daemon
2022-05-13 13:33 ` bugzilla-daemon
2022-05-13 13:50 ` bugzilla-daemon
2022-05-13 15:22 ` bugzilla-daemon
2022-05-15 21:38 ` bugzilla-daemon
2022-05-16  3:27 ` bugzilla-daemon
2022-05-16 10:23 ` bugzilla-daemon
2022-05-16 11:39 ` bugzilla-daemon
2022-05-16 12:16 ` bugzilla-daemon
2022-05-16 12:17 ` bugzilla-daemon
2022-05-18  7:48 ` bugzilla-daemon
2022-05-25 17:58 ` bugzilla-daemon
2022-06-03 13:45 ` bugzilla-daemon
2022-06-06 13:22 ` bugzilla-daemon
2022-06-16 10:38 ` bugzilla-daemon
2022-06-16 10:59 ` bugzilla-daemon
2022-06-16 11:21 ` bugzilla-daemon
2022-07-26 15:12 ` bugzilla-daemon

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=bug-215890-208809-pejxoC7N5j@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.