From: Greg KH <gregkh@suse.de>
To: "Denis V. Lunev" <den@sw.ru>
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, 6 Aug 2007 19:49:10 -0700 [thread overview]
Message-ID: <20070807024910.GB13657@suse.de> (raw)
In-Reply-To: <46B6CAC4.3080202@sw.ru>
On Mon, Aug 06, 2007 at 11:16:20AM +0400, Denis V. Lunev wrote:
> 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.
I don't think we really need to do fixups when we are "crashing" like
this. The user really isn't shutting down the kernel as it should
normally do.
Andrew, I really don't want to change the PCI core to handle this, as we
finally fixed a lot of issues with drivers trying to walk these lists
from interrupt context. So if you want to just hide the warning message
as we are shutting down, that's fine with me. Or just don't do the
fixups. But grabbing a reference to the pci device is unsafe in my
opinion and I do not want to do that.
thanks,
greg k-h
next prev parent reply other threads:[~2007-08-07 3:03 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
2007-08-07 2:49 ` Greg KH [this message]
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=20070807024910.GB13657@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=den@openvz.org \
--cc=den@sw.ru \
--cc=dev@openvz.org \
--cc=devel@openvz.org \
--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