linux-kernel - Re: libata & no PCI: dma_[un]map

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: <20070604171952.GA3437@dhcp83-182.boston.redhat.com>
Date:	Mon, 4 Jun 2007 13:19:52 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Christoph Hellwig <hch@...radead.org>,
	David Miller <davem@...emloft.net>, mroos@...ux.ee,
	linux-kernel@...r.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined

On Mon, Jun 04, 2007 at 08:47:19AM +0100, Christoph Hellwig wrote:
> The right fix is the depend on the new HAS_DMA (or whatever it's called)

ACK...  if the platform truly does not do DMA.


> symbol.  The proper long-term fix is to move calln to the dam mapping
> functions from the core libata files into the drivers responsibility with
> a default implementation for the typical cases.

NAK

We have generic devices and generic DMA mapping.  libata already uses
the generic stuff.  Now fix the platform...

	Jeff



-
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/