lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 6 Jan 2015 20:24:56 +0200 From: Aaro Koskinen <aaro.koskinen@....fi> To: Russell King - ARM Linux <linux@....linux.org.uk> Cc: Felipe Balbi <balbi@...com>, Tony Lindgren <tony@...mide.com>, Thomas Gleixner <tglx@...utronix.de>, Jason Cooper <jason@...edaemon.net>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>, Santosh Shilimkar <ssantosh@...nel.org>, Peter Kümmel <syntheticpp@....net>, Linux OMAP Mailing List <linux-omap@...r.kernel.org>, Linux ARM Kernel Mailing List <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH] irqchip: omap-intc: fix legacy DMA regression Hi, On Tue, Jan 06, 2015 at 06:05:32PM +0000, Russell King - ARM Linux wrote: > On Tue, Jan 06, 2015 at 10:51:33AM -0600, Felipe Balbi wrote: > > + * FIXME legacy OMAP DMA driver sitting under arch/arm/plat-omap/dma.c > > + * depends is still not ready for linear IRQ domains; because of that > > + * we need to temporarily "blacklist" OMAP2 and OMAP3 devices from using > > + * linear IRQ Domain until that driver is finally fixed. > > "finally fixed" or finally killed off like it really needs to be, once > all users of it are killed. > > We've been trying to do this for, what, three years now... I finally > pushed a WARN_ON() into that code to make it obvious to anyone who > uses omap_request_dma() that they really need to update their code. > Here's the list of references to that symbol which *still* need to be > fixed so that we can kill the legacy DMA driver: > > drivers/usb/gadget/udc/omap_udc.c: status = omap_request_dma(dma_channel, > drivers/usb/gadget/udc/omap_udc.c: status = omap_request_dma(dma_channel, I only learned about this after the WARN_ON() appeared in 3.17 (just couple months ago), and it's on my TODO list... A. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists