From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v4.20-rc3
Date: Fri, 23 Nov 2018 17:37:32 +0100 [thread overview]
Message-ID: <20181123163727.aa3hdbnne3aadypo@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Hi Linus,
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git iommu-fixes-v4.20-rc3
for you to fetch changes up to 829383e183728dec7ed9150b949cd6de64127809:
iommu/vt-d: Use memunmap to free memremap (2018-11-22 17:02:21 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v4.20-rc3
Including:
- Two fixes for the Intel VT-d driver to fix a NULL-ptr
dereference and an unbalance in an allocate/free path
(allocated with memremap, freed with iounmap)
- Fix for a crash in the Renesas IOMMU driver
- Fix for the Advanced Virtual Interrupt Controler (AVIC) code
in the AMD IOMMU driver
----------------------------------------------------------------
Filippo Sironi (1):
amd/iommu: Fix Guest Virtual APIC Log Tail Address Register
Geert Uytterhoeven (1):
iommu/ipmmu-vmsa: Fix crash on early domain free
Lu Baolu (1):
iommu/vt-d: Fix NULL pointer dereference in prq_event_thread()
Pan Bian (1):
iommu/vt-d: Use memunmap to free memremap
drivers/iommu/amd_iommu_init.c | 3 ++-
drivers/iommu/intel-iommu.c | 2 +-
drivers/iommu/intel-svm.c | 2 +-
drivers/iommu/ipmmu-vmsa.c | 3 +++
4 files changed, 7 insertions(+), 3 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2018-11-23 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181123163727.aa3hdbnne3aadypo@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).