From: linas@austin.ibm.com
To: linux-hotplug@vger.kernel.org
Subject: calling pci_find_device in interrupt ?
Date: Mon, 19 Jan 2004 21:15:31 +0000 [thread overview]
Message-ID: <20040119151531.C22416@forte.austin.ibm.com> (raw)
Greg,
I was calling pci_find_device() from an interrupt, when I discovered
that it has a WARN_ON(in_interrupt()); in it.
Why? If spin_lock(&pci_bus_lock); was changed to spin_lock_irqsave(),
it seems like it would be interrupt-safe.
Rather than sending a patch that makes this change, I thought I'd
enquire politely first ...
--linas
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-01-19 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 21:15 linas [this message]
2004-01-19 21:41 ` calling pci_find_device in interrupt ? Greg KH
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=20040119151531.C22416@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-hotplug@vger.kernel.org \
/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).