linux-kernel - Re: 4.3-rc3 BAR allocation problems on multiple machines

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: <20161026215047.GA28097@bhelgaas-glaptop.roam.corp.google.com>
Date:   Wed, 26 Oct 2016 16:50:47 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Meelis Roos <mroos@...ux.ee>
Cc:     Yinghai Lu <yinghai@...nel.org>,
        Linux Kernel list <linux-kernel@...r.kernel.org>,
        linux-pci@...r.kernel.org
Subject: Re: 4.3-rc3 BAR allocation problems on multiple machines

Hi Meelis,

On Wed, Oct 07, 2015 at 12:25:19PM +0300, Meelis Roos wrote:
> First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation 
> was failing for qla1280 scsi driver. Reading dmesg uncovered "can't 
> claim BAR" errors. Looking for this in my other test machines I see more 
> of them - on many sparc64 machines and some on x86.
> 
> In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu 
> asked for full dmesg to solve another similar case. So to help 
> understanding this one, here are the dmesgs of my machines:
> 
> sparc64 machines:
> 
> http://kodu.ut.ee/~mroos/dm/dm.t1-105
> http://kodu.ut.ee/~mroos/dm/dm.t1-200
> http://kodu.ut.ee/~mroos/dm/dm.v120
> http://kodu.ut.ee/~mroos/dm/dm.v210
> http://kodu.ut.ee/~mroos/dm/dm.v240
> http://kodu.ut.ee/~mroos/dm/dm.sb100
> 
> amd64 machine:
> 
> http://kodu.ut.ee/~mroos/dm/dm.x2100

I'm looking through the PCI bugs in bugzilla.kernel.org and came
across one that I opened for this issue
(https://bugzilla.kernel.org/show_bug.cgi?id=117191)

Is this still an issue?  I've applied some patches from Yinghai, but I
know there are a bunch more in the queue, so I'm trying to figure out
what's fixed and what's still broken.

Bjorn