linux-kernel - Re: [PATCH] x86: fix nommu_alloc_coherent allocation with NULL device argument

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: <20080905104910.GB17776@elte.hu>
Date:	Fri, 5 Sep 2008 12:49:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Joerg Roedel <joerg.roedel@....com>
Cc:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>, mingo@...hat.com,
	linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org
Subject: Re: [PATCH] x86: fix nommu_alloc_coherent allocation with NULL
	device argument


* Joerg Roedel <joerg.roedel@....com> wrote:

> I agree with this patch in principle. It fixes the problem. But I 
> think we should evaluate if we can change the dma_mask of the 
> fallback_dev to 24 bit.

ok - i kept this commit for now in tip/x86/iommu:

# 551b454: x86: gart alloc_coherent doesn't need to check NULL device argument

and will let you guys sort out how to do the others.

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