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:	Sun, 2 Aug 2009 22:18:27 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Matthew Wilcox <willy@...ux.intel.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Regression] PCI resources allocation problem on HP nx6325

On Sunday 02 August 2009, Matthew Wilcox wrote:
> On Sun, Aug 02, 2009 at 04:19:47PM +0200, Rafael J. Wysocki wrote:
> > Hi Matthew,
> > 
> > As reported at
> > 
> > http://bugzilla.kernel.org/show_bug.cgi?id=13891
> > 
> > there is a problem with allocating PCI resources on HP nx6325 introduced by
> > your commit a76117dfd687ec4be0a9a05214f3009cc5f73a42
> > (x86: Use pci_claim_resource).
> > 
> > On this particular box it causes the audio adapter's PCI memory space to
> > be allocated for something else.
> 
> Could you also attach lspci -v?  It seems that the 0000:00:12.0 resource
> is nesting inside the 0000:00:14.2 resource, which is just not possible.

It only looks like that in the failing case, though.

> Also, could you boot -rc5 (without
> a76117dfd687ec4be0a9a05214f3009cc5f73a42 reverted) with this patch
> applied?  It may give us some idea of what's going wrong.

I tested the Linus' patch replacing insert_resource() with request_resource()
and it worked, so do you still want me to provide this information?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ