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
| ||
|
Message-Id: <20190201084801.10983-1-hch@lst.de> Date: Fri, 1 Feb 2019 09:47:43 +0100 From: Christoph Hellwig <hch@....de> To: John Crispin <john@...ozen.org>, Vinod Koul <vkoul@...nel.org>, Dmitry Tarnyagin <dmitry.tarnyagin@...kless.no>, Nicolas Ferre <nicolas.ferre@...rochip.com>, Sudip Mukherjee <sudipm.mukherjee@...il.com>, Felipe Balbi <balbi@...nel.org>, linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org, netdev@...r.kernel.org, linux-usb@...r.kernel.org, linux-fbdev@...r.kernel.org, alsa-devel@...a-project.org Cc: iommu@...ts.linux-foundation.org Subject: don't pass a NULL struct device to DMA API functions We still have a few drivers which pass a NULL struct device pointer to DMA API functions, which generally is a bad idea as the API implementations rely on the device not only for ops selection, but also the dma mask and various other attributes. This series contains all easy conversions to pass a struct device, besides that there also is some arch code that needs separate handling, a driver that should not use the DMA API at all, and one that is a complete basket case to be deal with separately.
Powered by blists - more mailing lists