https://bugzilla.kernel.org/show_bug.cgi?id=215890 --- Comment #9 from Christoph Hellwig (hch@xxxxxx) --- 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@xxxxxxxxxx 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.
