linux-kernel - Re: [PATCH 0/3] fix alloc_coherent allocation issues (tip/x86/iommu)

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: <20080905181155W.fujita.tomonori@lab.ntt.co.jp>
Date:	Fri, 5 Sep 2008 18:11:41 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	mingo@...hat.com
Cc:	joerg.roedel@....com, linux-kernel@...r.kernel.org,
	iommu@...ts.linux-foundation.org
Subject: Re: [PATCH 0/3] fix alloc_coherent allocation issues
 (tip/x86/iommu)

On Fri,  5 Sep 2008 17:58:46 +0900
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:

> This patchset restores some of the current alloc_coherent behaviors
> that Joerg's x86 patchset (in tip/x86/iommu) changes.
> 
> The first patch uses __GFP_DMA for NULL device argument (fallback_dev)
> with pci-nommu. It's a hack for ISA (and some old code) so we need
> DMA_ZONE.
> 
> The second patch uses __GFP_NORETRY in the case of GFP_DMA.
> 
> The third patch is a minor cleanup.

Oops, I messed up the subjects. They should have been:

[PATCH 1/3] x86: fix nommu_alloc_coherent allocation with NULL device argument
[PATCH 2/3] x86: use __GFP_NORETRY in the case of GFP_DMA with pci-nommu
[PATCH 3/3] x86: gart alloc_coherent doesn't need to check NULL device argument

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