From: Joerg Roedel <jroedel@suse.de>
To: Qian Cai <cai@lca.pw>
Cc: tmurphy@arista.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] iommu/amd: fix a null-ptr-deref in map_sg()
Date: Wed, 12 Jun 2019 10:04:26 +0200 [thread overview]
Message-ID: <20190612080426.GL8151@suse.de> (raw)
In-Reply-To: <20190506164440.37399-1-cai@lca.pw>
On Mon, May 06, 2019 at 12:44:40PM -0400, Qian Cai wrote:
> The commit 1a1079011da3 ("iommu/amd: Flush not present cache in
> iommu_map_page")
That patch was reverted by me in
97a18f548548a6ee1b9be14c6fc72090b8839875
because it caused issues by testers. So maybe re-submit the above patch
with this fix included?
Regards,
Joerg
_______________________________________________
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 <jroedel@suse.de>
To: Qian Cai <cai@lca.pw>
Cc: tmurphy@arista.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] iommu/amd: fix a null-ptr-deref in map_sg()
Date: Wed, 12 Jun 2019 10:04:26 +0200 [thread overview]
Message-ID: <20190612080426.GL8151@suse.de> (raw)
In-Reply-To: <20190506164440.37399-1-cai@lca.pw>
On Mon, May 06, 2019 at 12:44:40PM -0400, Qian Cai wrote:
> The commit 1a1079011da3 ("iommu/amd: Flush not present cache in
> iommu_map_page")
That patch was reverted by me in
97a18f548548a6ee1b9be14c6fc72090b8839875
because it caused issues by testers. So maybe re-submit the above patch
with this fix included?
Regards,
Joerg
next prev parent reply other threads:[~2019-06-12 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 16:44 [PATCH -next v2] iommu/amd: fix a null-ptr-deref in map_sg() Qian Cai
2019-05-06 16:44 ` Qian Cai
2019-05-07 7:39 ` Joerg Roedel
2019-05-07 7:39 ` Joerg Roedel
2019-06-06 14:12 ` Tom Murphy via iommu
2019-06-06 14:12 ` Tom Murphy
2019-06-12 8:04 ` Joerg Roedel [this message]
2019-06-12 8:04 ` 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=20190612080426.GL8151@suse.de \
--to=jroedel@suse.de \
--cc=cai@lca.pw \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmurphy@arista.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.