linux-kernel - Re: [PATCH v11 04/60] sparc/PCI: Use correct offset for bus address to resource

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, 04 May 2016 00:17:05 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	benh@...nel.crashing.org
Cc:	yinghai@...nel.org, helgaas@...nel.org, bhelgaas@...gle.com,
	torvalds@...ux-foundation.org, weiyang@...ux.vnet.ibm.com,
	linux@....tj, wangyijing@...wei.com, khalid.aziz@...cle.com,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	mpe@...erman.id.au
Subject: Re: [PATCH v11 04/60] sparc/PCI: Use correct offset for bus
 address to resource

From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Date: Wed, 04 May 2016 10:37:40 +1000

> On Tue, 2016-05-03 at 15:52 -0700, Yinghai Lu wrote:
>> BenH and DavidM,
>> Are you ok to let /proc/bus/pci/devices to expose resource value
>> instead of
>> BAR value?
>> powerpc already expose MMIO as resource value, but still keep IO as
>> BAR value?
>> 
>> Or can we just dump /proc/bus/pci support from now?
> 
> The problem tends to be old Xserver expectations...
> 
> That stuff has been a can of worms over the years and we did things in
> the kernel to work around X limitations. I'm not that keen on touching
> /proc at all in that regard. Leave it there do what it does today, it's
> a user visible ABI, don't change it.

I agree with Ben, whatever procfs is exporting in the past is what
the Xserver and other things expect on sparc64 and therefore is a
user facing ABI that can't be changed.