linux-kernel - Re: d63e2e1f3df breaks sparc/T5-8

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: <20150327.145016.86183910134380870.davem@davemloft.net>
Date:	Fri, 27 Mar 2015 14:50:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	yinghai@...nel.org
Cc:	david.ahern@...cle.com, bhelgaas@...gle.com,
	linux-pci@...r.kernel.org, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: d63e2e1f3df breaks sparc/T5-8

From: Yinghai Lu <yinghai@...nel.org>
Date: Fri, 27 Mar 2015 14:01:54 -0700

> On Thu, Mar 26, 2015 at 4:27 PM, David Ahern <david.ahern@...cle.com> wrote:
>> On 3/26/15 2:43 PM, Yinghai Lu wrote:
>>>
>>> Can you send out boot log with "debug ignore_loglevel"?
>>
>>
>> attached
> 
> So the kernel config is sparc32 or sparc64 ?
> 
> pci 0000:06:00.0: reg 0x184: can't handle BAR above 4GB (bus address
> 0x110204000)
> 
> 
> only could happen when dma_addr_t is 32bit.

All DMA occurs behind an IOMMU and these IOMMUs only
support 32-bit addressing, therefore dma_addr_t is
32-bit on sparc64.

If you want to represent PCI address in some way, you
absolutely cannot use dma_addr_t as your data type.
--
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/