From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
Will Deacon <will.deacon@arm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
David Howells <dhowells@redhat.com>,
David Brown <david.brown@linaro.org>,
Peter Jones <pjones@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Nicolas Broeking <nbroeking@me.com>,
Jonathan Corbet <corbet@lwn.net>,
the arch/x86 maintainers <x86@kernel.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Vlastimil Babka <vbabka@suse.cz>,
Andy Gross <andy.gross@linaro.org>,
Darren Hart <dvhart@infradead.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
platform-driver-x86@vger.kernel.org,
Arend Van Spriel <arend.vanspriel@broadcom.com>,
Todd Kjos <tkjos@android.com>,
Kees
Subject: Re: Do Qualcomm drivers use DMA buffers for request_firmware_into_buf()?
Date: Thu, 28 Jun 2018 01:50:16 +0200 [thread overview]
Message-ID: <20180627235016.GD21242@wotan.suse.de> (raw)
In-Reply-To: <CAKv+Gu-mnjxFYwPZdGtgo5-mNhNgNih0BVxWxROVUzjqdBA9QQ@mail.gmail.com>
On Thu, Jun 28, 2018 at 01:42:52AM +0200, Ard Biesheuvel wrote:
> But what point is there to letting LSMs decide that they do not trust
> an I/O device if there is nothing we can do about it? How can we
> prevent such an I/O device from modifying our memory?
Simply LSMs can opt to not trust such setup. Its their choice.
The solution to addressing the concern is orthogonal to their
choice.
Luis
next prev parent reply other threads:[~2018-06-27 23:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180408174014.21908-1-hdegoede@redhat.com>
[not found] ` <20180408174014.21908-3-hdegoede@redhat.com>
[not found] ` <20180423211143.GZ14440@wotan.suse.de>
[not found] ` <71e6a45a-398d-b7a4-dab0-8b9936683226@redhat.com>
[not found] ` <1524586021.3364.20.camel@linux.vnet.ibm.com>
[not found] ` <20180424234219.GX14440@wotan.suse.de>
[not found] ` <1524632409.3371.48.camel@linux.vnet.ibm.com>
2018-04-25 17:55 ` [PATCH v3 2/5] efi: Add embedded peripheral firmware support Luis R. Rodriguez
2018-05-04 0:21 ` Luis R. Rodriguez
2018-05-04 15:26 ` Martijn Coenen
2018-05-04 19:44 ` Martijn Coenen
2018-05-08 15:38 ` Luis R. Rodriguez
2018-05-08 16:10 ` Luis R. Rodriguez
2018-06-07 16:49 ` Bjorn Andersson
2018-06-07 18:22 ` Luis R. Rodriguez
2018-06-01 19:23 ` Luis R. Rodriguez
2018-06-06 20:32 ` Do Qualcomm drivers use DMA buffers for request_firmware_into_buf()? Luis R. Rodriguez
2018-06-06 20:41 ` Ard Biesheuvel
2018-06-06 22:29 ` Luis R. Rodriguez
2018-06-06 22:41 ` Ard Biesheuvel
2018-06-06 22:55 ` Luis R. Rodriguez
2018-06-07 16:18 ` Bjorn Andersson
2018-06-07 16:23 ` Ard Biesheuvel
2018-06-07 16:33 ` Greg Kroah-Hartman
2018-06-07 16:43 ` Ard Biesheuvel
2018-06-07 16:49 ` Greg Kroah-Hartman
2018-06-07 16:56 ` Ard Biesheuvel
2018-06-07 18:21 ` Bjorn Andersson
2018-06-07 18:42 ` Ard Biesheuvel
2018-06-26 0:08 ` Bjorn Andersson
2018-06-27 18:00 ` Luis R. Rodriguez
2018-06-27 22:21 ` Ard Biesheuvel
2018-06-27 23:33 ` Luis R. Rodriguez
2018-06-27 23:42 ` Ard Biesheuvel
2018-06-27 23:50 ` Luis R. Rodriguez [this message]
2018-06-08 6:41 ` Vlastimil Babka
2018-06-07 18:06 ` Bjorn Andersson
2018-06-18 23:49 ` Luis R. Rodriguez
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=20180627235016.GD21242@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=andy.gross@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arend.vanspriel@broadcom.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=david.brown@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=nbroeking@me.com \
--cc=pjones@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tkjos@android.com \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=zohar@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox