linux-kernel - Re: [PATCH] pci_get_device call from interrupt in reboot fixups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070807024910.GB13657@suse.de>
Date:	Mon, 6 Aug 2007 19:49:10 -0700
From:	Greg KH <gregkh@...e.de>
To:	"Denis V. Lunev" <den@...ru>
Cc:	"Denis V. Lunev" <den@...nvz.org>, dev@...nvz.org,
	akpm@...ux-foundation.org, devel@...nvz.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pci_get_device call from interrupt in reboot fixups

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/