From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Myron Stowe <myron.stowe@redhat.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/PCI: add spinlock held check to 'pcibios_fwaddrmap_lookup()'
Date: Fri, 2 Mar 2012 12:04:10 -0800 [thread overview]
Message-ID: <20120302120410.27cea21c@jbarnes-desktop> (raw)
In-Reply-To: <20120302194501.26152.22845.stgit@amt.stowe>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
On Fri, 02 Mar 2012 12:45:01 -0700
Myron Stowe <myron.stowe@redhat.com> wrote:
> 'pcibios_fwaddrmap_lookup()' is used to maintain FW-assigned BIOS BAR
> values for reinstatement when normal resource assignment attempts
> fail and must be called with the 'pcibios_fwaddrmap_lock' spinlock
> held.
>
> This patch adds a WARN_ON notification if the spinlock is not currently
> held by the caller.
>
> Signed-off-by: Myron Stowe <myron.stowe@redhat.com>
> ---
>
> arch/x86/pci/i386.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/pci/i386.c b/arch/x86/pci/i386.c
> index 33e6a0b..831971e 100644
> --- a/arch/x86/pci/i386.c
> +++ b/arch/x86/pci/i386.c
> @@ -57,6 +57,8 @@ static struct pcibios_fwaddrmap *pcibios_fwaddrmap_lookup(struct pci_dev *dev)
> {
> struct pcibios_fwaddrmap *map;
>
> + WARN_ON(!spin_is_locked(&pcibios_fwaddrmap_lock));
> +
> list_for_each_entry(map, &pcibios_fwaddrmappings, list)
> if (map->dev == dev)
> return map;
>
>
Applied, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-02 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 19:45 [PATCH] x86/PCI: add spinlock held check to 'pcibios_fwaddrmap_lookup()' Myron Stowe
2012-03-02 20:00 ` Greg KH
2012-03-02 20:18 ` Myron Stowe
2012-03-02 20:24 ` Jesse Barnes
2012-03-02 20:41 ` Greg KH
2012-03-02 21:09 ` Jesse Barnes
2012-03-02 20:04 ` Jesse Barnes [this message]
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=20120302120410.27cea21c@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=myron.stowe@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).