From: Joerg Roedel <joro@8bytes.org>
To: Pan Bian <bianpan201602@163.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Pan Bian <bianpan2016@163.com>
Subject: Re: [PATCH 1/1] iommu/amd: fix incorrect error handling
Date: Mon, 24 Apr 2017 12:39:05 +0200 [thread overview]
Message-ID: <20170424103905.GH7266@8bytes.org> (raw)
In-Reply-To: <1492943001-1078-1-git-send-email-bianpan201602@163.com>
On Sun, Apr 23, 2017 at 06:23:21PM +0800, Pan Bian wrote:
> From: Pan Bian <bianpan2016@163.com>
>
> In function amd_iommu_bind_pasid(), the control flow jumps to label
> out_free when pasid_state->mm and mm is NULL. And mmput(mm) is called.
> In function mmput(mm), mm is referenced without validation. This will
> result in a NULL dereference bug. This patch fixes the bug.
>
> Signed-off-by: Pan Bian <bianpan2016@163.com>
Applied, thanks.
prev parent reply other threads:[~2017-04-24 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 10:23 [PATCH 1/1] iommu/amd: fix incorrect error handling Pan Bian
2017-04-24 10:39 ` 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=20170424103905.GH7266@8bytes.org \
--to=joro@8bytes.org \
--cc=bianpan201602@163.com \
--cc=bianpan2016@163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox