From: Bjorn Helgaas <bhelgaas@google.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Myron Stowe <mstowe@redhat.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org
Subject: Re: x86: runtime waring in pcibios_fwaddrmap_lookup
Date: Mon, 14 May 2012 14:21:47 -0600 [thread overview]
Message-ID: <20120514202147.GA20652@google.com> (raw)
In-Reply-To: <alpine.SOC.1.00.1205131811590.7097@math.ut.ee>
On Sun, May 13, 2012 at 06:15:18PM +0300, Meelis Roos wrote:
> > > Thanks for the quick response Meelis (unlike myself; I've been consumed
> > > with a hard deadline task recently - sorry).
>
> Not so quick this time - I had to replace the HDD and then recreate the
> failing config. Took 2.4-rc7 as a base. This gives us another data point
> - it does not warn on SMP but warns only on UP.
I think that's the critical point; thanks for mentioning it :)
The following patch should fix it. Can you confirm?
commit d7d1398aa087445ce04a1b1d45c4de7485590f57
Author: Bjorn Helgaas <bhelgaas@google.com>
Date: Mon May 14 12:01:26 2012 -0600
x86/PCI: only check for spinlock being held in SMP kernels
spin_is_locked() is always false on UP kernels: spin_lock_irqsave() does no
locking, so we can't tell whether the lock is held or not. Therefore,
this warning is only valid for SMP kernels.
Reported-and-tested-by: Meelis Roos <mroos@linux.ee>
CC: Myron Stowe <myron.stowe@redhat.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
diff --git a/arch/x86/pci/i386.c b/arch/x86/pci/i386.c
index 831971e..dd8ca6f 100644
--- a/arch/x86/pci/i386.c
+++ b/arch/x86/pci/i386.c
@@ -57,7 +57,7 @@ static struct pcibios_fwaddrmap *pcibios_fwaddrmap_lookup(struct pci_dev *dev)
{
struct pcibios_fwaddrmap *map;
- WARN_ON(!spin_is_locked(&pcibios_fwaddrmap_lock));
+ WARN_ON_SMP(!spin_is_locked(&pcibios_fwaddrmap_lock));
list_for_each_entry(map, &pcibios_fwaddrmappings, list)
if (map->dev == dev)
next prev parent reply other threads:[~2012-05-14 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 19:41 x86: runtime waring in pcibios_fwaddrmap_lookup Meelis Roos
2012-04-13 1:38 ` Bjorn Helgaas
2012-04-27 20:14 ` Myron Stowe
2012-04-28 5:36 ` Meelis Roos
2012-05-01 20:54 ` Myron Stowe
2012-05-07 22:44 ` Myron Stowe
2012-05-13 15:15 ` Meelis Roos
2012-05-14 20:21 ` Bjorn Helgaas [this message]
2012-05-14 20:53 ` Meelis Roos
2012-05-15 23:02 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120514202147.GA20652@google.com \
--to=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=mstowe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).