linux-kernel - Re: [RFC PATCH 13/18] ARM: LPAE: ensure dma_addr_t is the same size as phys_addr

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: <1288006329.14756.13.camel@e102109-lin.cambridge.arm.com>
Date:	Mon, 25 Oct 2010 12:32:09 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	linux-arm-kernel@...ts.infradead.org,
	Will Deacon <Will.Deacon@....com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 13/18] ARM: LPAE: ensure dma_addr_t is the same
 size as phys_addr_t

On Mon, 2010-10-25 at 12:08 +0100, Arnd Bergmann wrote:
> On Monday 25 October 2010, Catalin Marinas wrote:
> > From: Will Deacon <will.deacon@....com>
> >
> > Now that phys_addr_t can be 64-bit on ARM, we must ensure that dma_addr_t
> > is sufficiently large to hold physical addresses.
> >
> > This patch uses the types.h implementation in asm-generic to define the
> > dma_addr_t type as the same width as phys_addr_t.
> >
> > Signed-off-by: Will Deacon <will.deacon@....com>
> > Signed-off-by: Catalin Marinas <catalin.marinas@....com>
> 
> This patch will become obsolete once the "unify dma_addr_t typedef"
> series from Fujita Tomonori is upstream, you will instead have to set
> CONFIG_ARCH_DMA_ADDR_T_64BIT.

Yes, I know this and it's on my list to fix once I update the patches to
2.6.37-rc1.

Thanks,

Catalin

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