linux-kernel - Re: [Xen-devel] [PATCH] xen: use PCI interfaces to request IO and MEM resources on platform device.

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: <4D2C72FA020000780002BB58@vpn.id2.novell.com>
Date:	Tue, 11 Jan 2011 14:10:50 +0000
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Ian Campbell" <Ian.Campbell@...citrix.com>
Cc:	"Stefano Stabellini" <Stefano.Stabellini@...citrix.com>,
	"jeremy@...p.org" <jeremy@...p.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: use PCI interfaces to request IO
	 and MEM resources on platform device.

>>> On 11.01.11 at 14:01, Ian Campbell <Ian.Campbell@...citrix.com> wrote:
> The old way was correct circa 2.6.37-rc5 but broken in 2.6.37 final,
> there were a bunch of (reverts of) PCI resource changes in that window,
> If I had to make a guess I'd say it was something in there which did it.

Was it perhaps broken somewhere between -rc5 and -final, but
not in -final itself?

>> I'm mainly asking because if it really addresses some problem,
>> then unmodified_drivers/linux-2.6/platform-pci/platform-pci.c
>> in -unstable should probably get updated too.
> 
> Assuming the pci_* interfaces exist back as far as we care about for
> those drivers then I don't see why not to apply it.

I checked back to .5, where they exist; the question is - how far
back do we care?

Jan

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