From: Bjorn Helgaas <helgaas@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Simon Horman <horms@verge.net.au>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>,
Phil Edworthy <phil.edworthy@renesas.com>,
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
Date: Tue, 12 Dec 2017 11:16:58 -0600 [thread overview]
Message-ID: <20171212171658.GA53955@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <1512641720-4715-1-git-send-email-geert+renesas@glider.be>
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
next prev parent reply other threads:[~2017-12-12 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 10:15 [PATCH 0/2] PCI: rcar: Misc error path fixes Geert Uytterhoeven
2017-12-07 10:15 ` [PATCH 1/2] PCI: rcar: Fix use-after-free in probe error path Geert Uytterhoeven
2017-12-08 10:24 ` Lorenzo Pieralisi
2017-12-12 19:29 ` Bjorn Helgaas
2017-12-13 8:29 ` Simon Horman
2017-12-07 10:15 ` [PATCH 2/2] PCI: rcar: Handle rcar_pcie_parse_request_of_pci_ranges() failures Geert Uytterhoeven
2017-12-08 10:30 ` Lorenzo Pieralisi
2017-12-19 11:40 ` Lorenzo Pieralisi
2017-12-07 10:29 ` [PATCH 0/2] PCI: rcar: Misc error path fixes Simon Horman
2017-12-12 17:16 ` Bjorn Helgaas [this message]
2017-12-12 18:07 ` Geert Uytterhoeven
2017-12-12 18:10 ` Lorenzo Pieralisi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171212171658.GA53955@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=harunobu.kurokawa.dn@renesas.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=phil.edworthy@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).