public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] Fix PCI BAR size interpretation on 64-bit arches
@ 2005-06-10 21:22 Olof Johansson
  0 siblings, 0 replies; only message in thread
From: Olof Johansson @ 2005-06-10 21:22 UTC (permalink / raw)
  To: linux-kernel; +Cc: linux-pci, greg, akpm, linuxppc64-dev

Hi,

On 64-bit machines, PCI_BASE_ADDRESS_MEM_MASK and other mask constants
passed to pci_size() are 64-bit (for example ~0x0fUL). However, pci_size
does comparisons between the u32 arguments and the mask, which will fail
even though any result from pci_size is still just 32-bit.

Changing the mask argument to u32 seems the obvious thing to do, since
all arithmetic in the function is 32-bit and having a larger mask makes
no sense.

This triggered on a PPC64 system here where an adapter (VGA, as it
happened) had a memory region base of 0xfe000000 and a sz of the same,
matching the if (max == maxbase ...) test at the bottom of pci_size
but failing the mask comparison. Quite a corner case which I guess
explains why we haven't seen it until now.


Signed-off-by: Olof Johansson <olof@lixom.net>

Index: 2.6/drivers/pci/probe.c
===================================================================
--- 2.6.orig/drivers/pci/probe.c	2005-06-10 15:09:37.000000000 -0500
+++ 2.6/drivers/pci/probe.c	2005-06-10 15:43:36.000000000 -0500
@@ -125,7 +125,7 @@ static inline unsigned int pci_calc_reso
 /*
  * Find the extent of a PCI decode..
  */
-static u32 pci_size(u32 base, u32 maxbase, unsigned long mask)
+static u32 pci_size(u32 base, u32 maxbase, u32 mask)
 {
 	u32 size = mask & maxbase;	/* Find the significant bits */
 	if (!size)

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-06-10 22:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-10 21:22 [PATCH] Fix PCI BAR size interpretation on 64-bit arches Olof Johansson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox