linux-kernel - Re: [stable] [patch] fix 64-vbit prefetchable memory resource BARs

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] [day] [month] [year] [list]

Message-ID: <20081103204726.GB19936@kroah.com>
Date:	Mon, 3 Nov 2008 12:47:26 -0800
From:	Greg KH <greg@...ah.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	stable@...nel.org, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, Peter Chubb <peterc@...ato.unsw.edu.au>,
	jbarnes@...tuousgeek.org, matthew@....cx
Subject: Re: [stable] [patch] fix 64-vbit prefetchable memory resource BARs

On Mon, Nov 03, 2008 at 02:42:10PM -0600, Bjorn Helgaas wrote:
> On Sunday 12 October 2008 06:49:04 pm Peter Chubb wrote:
> > Since patch 6ac665c63dcac8fcec534a1d224ecbb8b867ad59
> > my infiniband controller hasn't worked.  This is because it has
> > 64-bit prefetchable memory, which was mistakenly being  taken to be
> > 32-bit memory.  The resource flags in this case are
> > PCI_BASE_ADDRESS_MEM_TYPE_64|PCI_BASE_ADDRESS_MEM_PREFETCH.
> > 
> > This patch checks only for the PCI_BASE_ADDRESS_MEM_TYPE_64 bit; thus
> > whether the region is prefetchable or not is ignored.  This fixes my
> > Infiniband.
> 
> I think this patch needs to be put in a 2.6.27-stable release.
> 
> Without it, we ignore the upper bits of 64-bit prefetchable BARs.
> 
> This is commit e354597cce8d219d135d65e585dc4f30323486b9 in Linus's
> tree.

Thanks for the info, we will queue it up.

greg k-h
--
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/