linux-kernel - Re: ACPI hotplug panic with current git head

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] [day] [month] [year] [list]

Date:	Fri, 13 Feb 2009 16:30:03 -0800
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
Cc:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	Len Brown <lenb@...nel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel" <linux-kernel@...r.kernel.org>,
	"Li, Shaohua" <shaohua.li@...el.com>,
	Grant Grundler <grundler@...isc-linux.org>
Subject: Re: ACPI hotplug panic with current git head

On Wednesday, January 28, 2009 3:47 am Kenji Kaneshige wrote:
> I made several patches to fix the wrong assumption described
> above. It is very difficult for me to check all the code that
> refers pci_bus->self. So I checked include/linux/pci-acpi.h and
> the code under drivers/pci/ only. And I made patches for the code
> like below:
>
>  - The code that clearly chooses host bridge operation or
>    PCI-to-PCI bridge operation based on pci_bus->self.
>
>  - The code that might cause endless loop if pci_bus->self is
>    not NULL on the PCI root bus.

Kenji-san, can you re-send these to my private mail so I can apply them?  
(Outlook/Exchange can't let plain text through without molesting it for some 
reason.)

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/