From: "Denis V. Lunev" <den@sw.ru>
To: Greg KH <gregkh@suse.de>
Cc: "Denis V. Lunev" <den@openvz.org>,
dev@openvz.org, akpm@linux-foundation.org, devel@openvz.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci_get_device call from interrupt in reboot fixups
Date: Mon, 06 Aug 2007 11:16:20 +0400 [thread overview]
Message-ID: <46B6CAC4.3080202@sw.ru> (raw)
In-Reply-To: <20070804040806.GF23330@suse.de>
Greg KH wrote:
> On Fri, Aug 03, 2007 at 02:39:24PM +0400, Denis V. Lunev wrote:
>> The following calltrace is possible now:
>> handle_sysrq
>> machine_emergency_restart
>> mach_reboot_fixups
>> pci_get_device
>> pci_get_subsys
>> down_read
>> The patch obtains PCI device during initialization to avoid bothering PCI
>> search engine in interrupt. Devices used in this code are not supposed to
>> be pluggable, so it looks safe to keep them.
>
> What devices are supposed to be affected here? Are you sure that they
> can't be removed later? Grabbing references here might mess with them
> in the future.
Right now the list is the following:
static struct device_fixup fixups_table[] = {
{ PCI_VENDOR_ID_CYRIX, PCI_DEVICE_ID_CYRIX_5530_LEGACY,
cs5530a_warm_reset },
{ PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_CS5536_ISA, cs5536_warm_reset },
};
Though, if the approach is not suitable, we can skip fixups if we came
from sysrq.
Regards,
Den
next prev parent reply other threads:[~2007-08-06 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 10:39 [PATCH] pci_get_device call from interrupt in reboot fixups Denis V. Lunev
2007-08-04 4:08 ` Greg KH
2007-08-06 7:16 ` Denis V. Lunev [this message]
2007-08-07 2:49 ` Greg KH
2007-08-07 7:24 ` Andrew Morton
2007-08-07 7:44 ` Andrew Morton
2007-08-07 7:42 ` Greg KH
2007-08-07 7:50 ` Denis V. Lunev
2007-08-07 7:48 ` Denis V. Lunev
2007-08-06 20:03 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2007-08-07 9:04 Denis V. Lunev
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=46B6CAC4.3080202@sw.ru \
--to=den@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=den@openvz.org \
--cc=dev@openvz.org \
--cc=devel@openvz.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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