netdev - Re: [RFC] r8169 DMA failure with iommu=off

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] [day] [month] [year] [list]

Message-Id: <20150501.214606.1559227616669665075.davem@davemloft.net>
Date:	Fri, 01 May 2015 21:46:06 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	shemming@...cade.com
Cc:	romieu@...zoreil.com, eric.dumazet@...il.com,
	netdev@...r.kernel.org
Subject: Re: [RFC] r8169 DMA failure with iommu=off

From: Stephen Hemminger <shemming@...cade.com>
Date: Wed, 29 Apr 2015 16:58:13 -0700

> In either case since this is a receive DMA buffer, it should set
> the appropriate GFP_DMA since that may matter on some platforms.

Plain GFP_DMA is really only appropriate when used for ISA DMA
situations where we must have 24-bit addresses or whatever that
restriction was.

Anyways, it is dma_map_single()'s job to restrict DMA addressing if
necessary.  Otherwise, the transmit path would not work at all.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html