[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo5LMj=wPwYgJfk97hfx9b03fPHZXEvdR6gV2somBTD+4A@mail.gmail.com>
Date: Tue, 18 Sep 2012 16:46:46 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
x86@...nel.org, Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH] PCI, x86: clear initial value for root info resources
On Fri, Sep 14, 2012 at 6:48 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> Found one system one root bus hot remove get panic.
> Panic happens when try to release hostbridge resource.
>
> It turns out that resource get reject during put into resource tree
> because of conflicts.
> Also that resource parent pointer have random value.
>
> That invalid value cause it pass through check __release_pci_root_info
> and panic in release_resource.
>
> Try to use kzalloc instead.
Don't we need the same fix for ia64 in pci_acpi_scan_root()? Here's
what it does:
if (windows) {
controller->window =
kmalloc_node(sizeof(*controller->window) * windows,
GFP_KERNEL, controller->node);
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
> Cc: x86@...nel.org
>
> ---
> arch/x86/pci/acpi.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Index: linux-2.6/arch/x86/pci/acpi.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/pci/acpi.c
> +++ linux-2.6/arch/x86/pci/acpi.c
> @@ -305,7 +305,6 @@ setup_resource(struct acpi_resource *acp
> res->flags = flags;
> res->start = start;
> res->end = end;
> - res->child = NULL;
>
> if (!pci_use_crs) {
> dev_printk(KERN_DEBUG, &info->bridge->dev,
> @@ -434,7 +433,7 @@ probe_pci_root_info(struct pci_root_info
>
> size = sizeof(*info->res) * info->res_num;
> info->res_num = 0;
> - info->res = kmalloc(size, GFP_KERNEL);
> + info->res = kzalloc(size, GFP_KERNEL);
> if (!info->res)
> return;
>
--
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/
Powered by blists - more mailing lists