linux-kernel - Re: No dma_sync_* during pci_probe? (Sparc, post 2.6.22 regression)

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]

Date:	Wed, 19 Dec 2007 17:33:05 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	David Miller <davem@...emloft.net>
CC:	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org,
	gregkh@...e.de, krh@...planet.net,
	linux1394-devel@...ts.sourceforge.net
Subject: Re: No dma_sync_* during pci_probe? (Sparc, post 2.6.22 regression)

David Miller wrote:
> From: Stefan Richter <stefanr@...6.in-berlin.de>
> Date: Tue, 18 Dec 2007 11:38:27 +0100
> 
>> Also note:
>>   - The very same code did not oops at this point in 2.6.22.  It only
>>     started doing so in 2.6.23.
> 
> 2.6.23 is when the sparc64 IOMMU code started relying upon
> the dev_archdata bits being correct.

And why are the dev_archdata corrupt?
Does arch/sparc64/kernel/pci.c fill them in incorrectly or too late?

drivers/firewire/fw_ohci.c needs them for dma_map_single() +
dma_sync_single_for_device() in the pci_driver.probe(), sometime after
it called pci_enable_device(), before finishing the probe.
-- 
Stefan Richter
-=====-=-=== ==-- =--==
http://arcgraph.de/sr/
--
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/