From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756048AbcFTRXX (ORCPT ); Mon, 20 Jun 2016 13:23:23 -0400 Received: from foss.arm.com ([217.140.101.70]:34713 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752691AbcFTRWL (ORCPT ); Mon, 20 Jun 2016 13:22:11 -0400 Date: Mon, 20 Jun 2016 18:22:40 +0100 From: Lorenzo Pieralisi To: Tyler Baker Cc: Bjorn Helgaas , 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 , S??ren Brinkmann , linux-arm-kernel , "Kevin's boot bot" , Alex Benn??e Subject: Re: [PATCH v1 15/25] PCI: generic: Free resource list close to where it's allocated Message-ID: <20160620172240.GA30625@red-moon> References: <20160606225630.20936.77349.stgit@bhelgaas-glaptop2.roam.corp.google.com> <20160606230636.20936.29083.stgit@bhelgaas-glaptop2.roam.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 20, 2016 at 09:56:45AM -0700, Tyler Baker wrote: > 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). That's most likely because pci_ecam_create() requires the bus_range resource (its busr parameter) to be initialized when it is called and that's not the case after this patch is applied if I read it correctly. It is probably a NULL pointer dereference in pci_ecam_create(). Thanks, Lorenzo > > 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 > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >