[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0809011047530.12958@nehalem.linux-foundation.org>
Date: Mon, 1 Sep 2008 10:53:04 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Yinghai Lu <yhlu.kernel@...il.com>
cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jeff Garzik <jeff@...zik.org>, Tejun Heo <htejun@...il.com>,
Ingo Molnar <mingo@...e.hu>,
David Witbrodt <dawitbro@...global.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Kernel Testers <kernel-testers@...r.kernel.org>
Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit
a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
On Sun, 31 Aug 2008, Yinghai Lu wrote:
>
> how about
>
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index cce2f4c..3b5269a 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -240,6 +240,11 @@ static int __pci_read_base(struct pci_dev *dev,
> enum pci_bar_type type,
> pci_read_config_dword(dev, pos, &l);
> pci_write_config_dword(dev, pos, mask);
> pci_read_config_dword(dev, pos, &sz);
> +
> + /* sticky and non changable */
> + if (sz == l)
> + goto fail;
No, because a resource really _can_ be at the end. It's perfectly ok to
have something like a memory resource at 0xff000000-0xffffffff, and then
the BAR register would always read 0xff000000 (or 0x...4 for a 64-bit
resource).
So calling that a failure case would be wrong.
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/
Powered by blists - more mailing lists