From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755994AbcFTQ5q (ORCPT ); Mon, 20 Jun 2016 12:57:46 -0400 Received: from mail-qk0-f173.google.com ([209.85.220.173]:35079 "EHLO mail-qk0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754358AbcFTQ5k (ORCPT ); Mon, 20 Jun 2016 12:57:40 -0400 MIME-Version: 1.0 In-Reply-To: <20160606230636.20936.29083.stgit@bhelgaas-glaptop2.roam.corp.google.com> References: <20160606225630.20936.77349.stgit@bhelgaas-glaptop2.roam.corp.google.com> <20160606230636.20936.29083.stgit@bhelgaas-glaptop2.roam.corp.google.com> From: Tyler Baker Date: Mon, 20 Jun 2016 09:56:45 -0700 Message-ID: Subject: Re: [PATCH v1 15/25] PCI: generic: Free resource list close to where it's allocated To: Bjorn Helgaas Cc: linux-pci@vger.kernel.org, Thomas Petazzoni , Rob Herring , Jason Cooper , Scott Branden , Jon Mason , Jingoo Han , Pratyush Anand , "linux-kernel@vger.kernel.org" , rfi@lists.rocketboards.org, linux-renesas-soc@vger.kernel.org, Simon Horman , Thierry Reding , Tanmay Inamdar , Ray Jui , linux-tegra@vger.kernel.org, Ley Foon Tan , Michal Simek , =?UTF-8?Q?S=C3=B6ren_Brinkmann?= , linux-arm-kernel , "Kevin's boot bot" , =?UTF-8?B?QWxleCBCZW5uw6ll?= Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bjorn, On 6 June 2016 at 16:06, Bjorn Helgaas wrote: > Previously we allocated the PCI resource list in > gen_pci_parse_request_of_pci_ranges(), but if we had an error, we freed it > on error in gen_pci_init(). > > Reorder gen_pci_init() so we can take care of error path cleanup in > gen_pci_parse_request_of_pci_ranges() instead. > > Signed-off-by: Bjorn Helgaas The kernelci.org bot has reported[0] new qemu-aarch64 (arm64-defconfig) boot failures[1][2] in next-20160620. I've bisected[3] this boot failure down to this patch, and confirmed reverting it on top of next-20160620 resolves the boot issue. I have not investigated further, but you can easily reproduce[4] the boot failure on an x86 host running qemu-system-aarch64 (I'm running qemu-system 2.6). Cheers, Tyler [0] https://kernelci.org/boot/all/job/next/kernel/next-20160620/ [1] https://storage.kernelci.org/next/next-20160620/arm64-defconfig/lab-cambridge/boot-apm-mustang-kvm-guest.txt [2] https://storage.kernelci.org/next/next-20160620/arm64-defconfig/lab-tbaker/boot-qemu-aarch64,legacy.txt [3] http://hastebin.com/segiruribu.vbs [4] http://hastebin.com/dafuzicuyi.avrasm