From: Joerg Roedel <joro@8bytes.org>
To: Yuan Can <yuancan@huawei.com>
Cc: will@kernel.org, robin.murphy@arm.com, timur@tabi.org,
alex.williamson@redhat.com, Varun.Sethi@freescale.com,
iommu@lists.linux.dev
Subject: Re: [PATCH] iommu/fsl_pamu: Fix resource leak in fsl_pamu_probe()
Date: Tue, 22 Nov 2022 09:37:28 +0100 [thread overview]
Message-ID: <Y3yKSLllyolauQ0j@8bytes.org> (raw)
In-Reply-To: <20221121082022.19091-1-yuancan@huawei.com>
On Mon, Nov 21, 2022 at 08:20:22AM +0000, Yuan Can wrote:
> The fsl_pamu_probe() returns directly when create_csd() failed, leaving
> irq and memories unreleased.
> Fix by jumping to error if create_csd() returns error.
>
> Fixes: 695093e38c3e ("iommu/fsl: Freescale PAMU driver and iommu implementation.")
> Signed-off-by: Yuan Can <yuancan@huawei.com>
> ---
> drivers/iommu/fsl_pamu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
prev parent reply other threads:[~2022-11-22 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:20 [PATCH] iommu/fsl_pamu: Fix resource leak in fsl_pamu_probe() Yuan Can
2022-11-22 8:37 ` Joerg Roedel [this message]
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=Y3yKSLllyolauQ0j@8bytes.org \
--to=joro@8bytes.org \
--cc=Varun.Sethi@freescale.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=timur@tabi.org \
--cc=will@kernel.org \
--cc=yuancan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.