From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Phil Edworthy <phil.edworthy@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa@the-dreams.de>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 3/4] PCI: rcar: Add missing irq_dispose_mapping() into failpath
Date: Tue, 22 May 2018 23:51:09 +0200 [thread overview]
Message-ID: <a95615e8-69f7-886e-f659-6b9880debf28@gmail.com> (raw)
In-Reply-To: <CAMuHMdV9_-MRLDP98G5J5v1bojAUmRLvSkyf3Fhmn41t1rpn4g@mail.gmail.com>
On 05/22/2018 05:18 PM, Geert Uytterhoeven wrote:
> Hi Marek,
Hi,
> On Mon, May 21, 2018 at 3:11 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>> The rcar_pcie_get_resources() is another misnomer with a side effect.
>> The function does not only get resources, but also maps MSI IRQs via
>> irq_of_parse_and_map(). In case anything fails afterward, the IRQ
>> mapping must be disposed through irq_dispose_mapping() which is not
>> done.
>>
>> This patch handles irq_of_parse_and_map() failures in by disposing
>> of the mapping in rcar_pcie_get_resources() as well as in probe.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
>> --- a/drivers/pci/host/pcie-rcar.c
>> +++ b/drivers/pci/host/pcie-rcar.c
>> @@ -923,18 +923,25 @@ static int rcar_pcie_get_resources(struct rcar_pcie *pcie)
>> i = irq_of_parse_and_map(dev->of_node, 0);
>> if (!i) {
>> dev_err(dev, "cannot get platform resources for msi interrupt\n");
>> - return -ENOENT;
>> + err = -ENOENT;
>> + goto err_irq1;
>
> You could have kept the return here.
I like the symmetry ;-)
[...]
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-05-22 23:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 13:11 [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges() Marek Vasut
2018-05-21 13:11 ` [PATCH 2/4] PCI: rcar: Pull bus clock enable/disable from rcar_pcie_get_resources() Marek Vasut
2018-05-22 9:13 ` Simon Horman
2018-05-22 15:11 ` Geert Uytterhoeven
2018-05-21 13:11 ` [PATCH 3/4] PCI: rcar: Add missing irq_dispose_mapping() into failpath Marek Vasut
2018-05-22 9:14 ` Simon Horman
2018-05-22 15:18 ` Geert Uytterhoeven
2018-05-22 21:51 ` Marek Vasut [this message]
2018-05-21 13:11 ` [PATCH 4/4] PCI: rcar: Teardown MSI setup if rcar_pcie_enable() fails Marek Vasut
2018-05-22 9:16 ` Simon Horman
2018-05-22 18:36 ` Geert Uytterhoeven
2018-05-22 21:53 ` Marek Vasut
2018-05-23 6:18 ` Geert Uytterhoeven
2018-05-23 10:38 ` Marek Vasut
2018-05-22 9:12 ` [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges() Simon Horman
2018-05-22 10:53 ` Geert Uytterhoeven
2018-05-23 16:17 ` Lorenzo Pieralisi
2018-05-23 17:05 ` Marek Vasut
2018-05-23 21:56 ` Bjorn Helgaas
2018-05-24 7:24 ` Marek Vasut
2018-05-24 13:50 ` Lorenzo Pieralisi
2018-05-24 14:36 ` Marek Vasut
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=a95615e8-69f7-886e-f659-6b9880debf28@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=phil.edworthy@renesas.com \
--cc=wsa@the-dreams.de \
/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).