linux-kernel - Re: PCI BAR mem resource allocation "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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0812130901370.3340@localhost.localdomain>
Date:	Sat, 13 Dec 2008 09:16:29 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alex Chiang <achiang@...com>
cc:	matthew@....cx, justin.chen@...com, linux-kernel@...r.kernel.org
Subject: Re: PCI BAR mem resource allocation "regression"



On Fri, 12 Dec 2008, Alex Chiang wrote:
> 
> I've been chasing a bug for the past week or so that I can't seem
> to figure out, and was hoping to get your eyes on it.
> 
> The basic summary is, we can't allocate a memory resource for our
> BAR after a PCI hotplug operation. We've been able to bisect it
> down to d33b6fba2c4350651f3f61ff2ab858a2f116e9a4 (Resources:
> insert identical resources above existing resources).

I'm missing some pieces I'd like to see: /proc/iomem before and after, and 
lspci output before and after (you do give lspci output, but only one, and 
I can't tell if it's before or after).

Also, is it just the error message, or does it actually affect 
functionality?

			Linus
--
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/