From: Matthew Garrett <mjg59@google.com>
To: linux-efi <linux-efi@vger.kernel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
x86@kernel.org, linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [EFI,PCI] Allow disabling PCI busmastering on bridges during boot
Date: Mon, 2 Dec 2019 16:42:57 -0800 [thread overview]
Message-ID: <CACdnJus7nHdr4p4H1j5as9eB=FG-uX+wy_tjvTQ5ObErDJHdow@mail.gmail.com> (raw)
In-Reply-To: <20191203004043.174977-1-matthewgarrett@google.com>
On Mon, Dec 2, 2019 at 4:40 PM Matthew Garrett
<matthewgarrett@google.com> wrote:
>
> Add an option to disable the busmaster bit in the control register on
> all PCI bridges before calling ExitBootServices() and passing control to
> the runtime kernel. System firmware may configure the IOMMU to prevent
> malicious PCI devices from being able to attack the OS via DMA. However,
> since firmware can't guarantee that the OS is IOMMU-aware, it will tear
> down IOMMU configuration when ExitBootServices() is called. This leaves
> a window between where a hostile device could still cause damage before
> Linux configures the IOMMU again.
I don't know enough about ARM to know if this makes sense there as well. Anyone?
next prev parent reply other threads:[~2019-12-03 0:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 0:40 [PATCH] [EFI,PCI] Allow disabling PCI busmastering on bridges during boot Matthew Garrett
2019-12-03 0:42 ` Matthew Garrett [this message]
2019-12-03 11:54 ` Ard Biesheuvel
2019-12-03 13:38 ` Laszlo Ersek
2019-12-03 19:36 ` Matthew Garrett
2019-12-03 19:40 ` Matthew Garrett
2019-12-04 7:11 ` Laszlo Ersek
2019-12-04 19:29 ` Matthew Garrett
2019-12-03 15:30 ` Andy Lutomirski
2019-12-03 16:33 ` Ard Biesheuvel
2019-12-03 19:41 ` Matthew Garrett
2019-12-04 19:50 ` Andy Lutomirski
2019-12-04 19:56 ` Matthew Garrett
2019-12-12 15:46 ` Ard Biesheuvel
2019-12-13 21:24 ` Matthew Garrett
2019-12-03 18:23 ` kbuild test robot
2019-12-05 13:04 ` kbuild test robot
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='CACdnJus7nHdr4p4H1j5as9eB=FG-uX+wy_tjvTQ5ObErDJHdow@mail.gmail.com' \
--to=mjg59@google.com \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).