linux-kernel - Re: [Regression] PCI resources allocation problem on HP nx6325

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: <alpine.LFD.2.01.0908131113580.28882@localhost.localdomain>
Date:	Thu, 13 Aug 2009 11:16:17 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Manuel Lauss <mano@...rinelk.homelinux.net>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Matthew Wilcox <willy@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andrew Patterson <andrew.patterson@...com>
Subject: Re: [Regression] PCI resources allocation problem on HP nx6325



On Tue, 11 Aug 2009, Manuel Lauss wrote:
> 
> > So this patch is not something that I'm going to apply to my tree, but 
> > it's worth testing out to just verify that yes, I finally understand 
> > exactly what's going on. Because if I'm right, your warning will now go 
> > away (and it could be replaced by _other_ issues, of course ;).
> 
> The warning is gone, and /proc/iomem is identical to 2.6.30.
> I'd say you've hit the nail on the head ;)

Ok, thanks.

I'm not going to do anything about it right now, since clearly we've not 
changed any actual behavior from before. But if you remind me after 2.6.31 
is out, I'll look at perhaps making a better "pci_claim_resource()" that 
actually iterates over the different parent resources and doesn't just try 
to find one (and then fail if that particular one doesn't work out).

		Thanks,
			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/