From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752373AbdLLRRL (ORCPT ); Tue, 12 Dec 2017 12:17:11 -0500 Received: from mail.kernel.org ([198.145.29.99]:55890 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751274AbdLLRRF (ORCPT ); Tue, 12 Dec 2017 12:17:05 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AF3CA20740 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Tue, 12 Dec 2017 11:16:58 -0600 From: Bjorn Helgaas To: Geert Uytterhoeven Cc: Simon Horman , Lorenzo Pieralisi , Bjorn Helgaas , Harunobu Kurokawa , Phil Edworthy , linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] PCI: rcar: Misc error path fixes Message-ID: <20171212171658.GA53955@bhelgaas-glaptop.roam.corp.google.com> References: <1512641720-4715-1-git-send-email-geert+renesas@glider.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1512641720-4715-1-git-send-email-geert+renesas@glider.be> 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 Thu, Dec 07, 2017 at 11:15:18AM +0100, Geert Uytterhoeven wrote: > Hi Simon, Lorenzo, Bjorn, > > This patch series fixes two issues in the error path for the R-Car PCIe > host bridge driver. > > The first issue is triggered easily by not having a PCIe card inserted, > and may cause a crash. > > Thanks! > > Geert Uytterhoeven (2): > PCI: rcar: Fix use-after-free in probe error path > PCI: rcar: Handle rcar_pcie_parse_request_of_pci_ranges() failures > > drivers/pci/host/pcie-rcar.c | 11 +++++++---- > 1 file changed, 7 insertions(+), 4 deletions(-) The first fixes ddd535f1ea3eb27e, which appeared in v4.14-rc1. The second fixes 5d2917d469faab72, which appeared in v4.5-rc1. After the merge window I normally just pull in critical fixes and fixes to things we merged during the window. I think the first makes sense for v4.15 because it can cause a crash with no obvious way to debug it. The second one feels like v4.16 material to me. Thoughts? We're trying to sort out how to handle this sort of thing between Lorenzo and myself, so I apologize for the confusion here. Bjorn