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: <20160310183033.GA18456@localhost>
Date:	Thu, 10 Mar 2016 12:30:33 -0600
From:	Bjorn Helgaas <helgaas@...nel.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	David Miller <davem@...emloft.net>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Wei Yang <weiyang@...ux.vnet.ibm.com>, TJ <linux@....tj>,
	Yijing Wang <wangyijing@...wei.com>,
	Khalid Aziz <khalid.aziz@...cle.com>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v10 00/59] PCI: Resource allocation cleanup for v4.6

On Wed, Feb 24, 2016 at 06:11:51PM -0800, Yinghai Lu wrote:
> Hi,
> 
> After 5b28541552ef (PCI: Restrict 64-bit prefetchable bridge windows
> to 64-bit resources), we have several reports on resource allocation
> failure, and we try to fix the problem with resource clip, and find
> more problems.
> 
> One is realloc fail with two graphics cards above 4G.
> One is from sparc that have problem with clip as we don't parse
> mem64 for it.
> 
> Other report is about pci remove/rescan does not work on some setup
> when BIOS tend to allocate small bus size.
> 
> This patchset enhance resource allocation to address those problems.
> 
> patch 1-10: parse MEM64 for sparc and other system with OF
> ...

> Yinghai Lu (59):
>   PCI: Add pci_find_root_bus_resource()
>   sparc/PCI: Use correct bus address to resource offset
>   sparc/PCI: Reserve legacy mmio after PCI mmio
>   sparc/PCI: Add IORESOURCE_MEM_64 for 64-bit resource in OF parsing
>   sparc/PCI: Keep resource idx order with bridge register number
>   PCI: Kill wrong quirk about M7101
>   PCI: Ignore BAR for ALi M1533 PCI-ISA bridge

I took a look at the above and responded on the list with several
questions.  I have the feeling that some are because I'm missing
important details about how sparc works.  If it's easier to educate me
about those via IRC, I'm usually in #linux-pci on OFTC, and I'd be
happy to chat there.

Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ