From: Joerg Roedel <joro@8bytes.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: iommu@lists.linux-foundation.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org, eric.auger.pro@gmail.com
Subject: Re: [PATCH] iommu/vt-d: Fix leak in intel_pasid_alloc_table on error path
Date: Fri, 3 May 2019 17:34:43 +0200 [thread overview]
Message-ID: <20190503153443.GD11605@8bytes.org> (raw)
In-Reply-To: <20190430073004.10528-1-eric.auger@redhat.com>
On Tue, Apr 30, 2019 at 09:30:04AM +0200, Eric Auger wrote:
> If alloc_pages_node() fails, pasid_table is leaked. Free it.
>
> Fixes: cc580e41260db ("iommu/vt-d: Per PCI device pasid table interfaces")
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> ---
> drivers/iommu/intel-pasid.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, dwmw2@infradead.org
Subject: Re: [PATCH] iommu/vt-d: Fix leak in intel_pasid_alloc_table on error path
Date: Fri, 3 May 2019 17:34:43 +0200 [thread overview]
Message-ID: <20190503153443.GD11605@8bytes.org> (raw)
In-Reply-To: <20190430073004.10528-1-eric.auger@redhat.com>
On Tue, Apr 30, 2019 at 09:30:04AM +0200, Eric Auger wrote:
> If alloc_pages_node() fails, pasid_table is leaked. Free it.
>
> Fixes: cc580e41260db ("iommu/vt-d: Per PCI device pasid table interfaces")
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> ---
> drivers/iommu/intel-pasid.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied, thanks.
next prev parent reply other threads:[~2019-05-03 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 7:30 [PATCH] iommu/vt-d: Fix leak in intel_pasid_alloc_table on error path Eric Auger
2019-04-30 7:30 ` Eric Auger
2019-05-03 15:34 ` Joerg Roedel [this message]
2019-05-03 15:34 ` Joerg Roedel
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=20190503153443.GD11605@8bytes.org \
--to=joro@8bytes.org \
--cc=dwmw2@infradead.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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.