linux-kernel - Re: [PATCH] dma: remove bad_dma

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160613115911.GG2282@sirena.org.uk>
Date:	Mon, 13 Jun 2016 12:59:11 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Simran Rai <ssimran@...adcom.com>,
	Christoph Hellwig <hch@....de>
Subject: Re: [PATCH] dma: remove bad_dma_ops to fix build fail

On Mon, Jun 13, 2016 at 11:51:08AM +0100, Sudip Mukherjee wrote:
> On Mon, Jun 13, 2016 at 10:29:34AM +0100, Mark Brown wrote:

> > Right, we've got a couple of obscure architectures with no DMA support
> > which are leading to a constant stream of patches like this that are
> > being triggered by compile coverage stuff.  In situations like this we
> > very often provide stubs rather than having to handle this in lots of
> > different places in the code.

> Ok, I will do that. But I am seeing arch/m32r/include/asm/m32102.h is
> defining the DMA Controller registers and also a MAX_DMA_ADDRESS is
> defined in dma.h. Doesn't that mean that this arch is capable of DMA?

Quite possibly, but they don't seem to implement the standard interfaces
for generic code (this sort of thing is quite common for the less widely
used architectures sadly).

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)