From: David Brazdil <dbrazdil@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Frank Rowand <frowand.list@gmail.com>,
David Brazdil <dbrazdil@google.com>,
Will Deacon <will@kernel.org>, Andrew Scull <ascull@google.com>,
Wedson Almeida Filho <wedsonaf@google.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/2] Driver for Open Profile for DICE
Date: Wed, 26 Jan 2022 23:12:35 +0000 [thread overview]
Message-ID: <20220126231237.529308-1-dbrazdil@google.com> (raw)
Open Profile for DICE is an open protocol for measured boot compatible
with the Trusted Computing Group's Device Identifier Composition
Engine (DICE) specification. The generated Compound Device Identifier
(CDI) certificates represent the measured hardware/software combination
and can be used by userspace for remote attestation and sealing.
This patchset adds DeviceTree bindings for the DICE device referencing
a reserved memory region containing the CDIs, and a driver that exposes
the memory region to userspace via a misc device.
See https://pigweed.googlesource.com/open-dice for more details.
The patches are based on top of v5.17-rc1 and can also be found here:
https://android-kvm.googlesource.com/linux topic/dice_v7
Changes since v6:
* replace spinlock with mutex because devm_memremap can sleep
* prevent write+shared mapping via mprotect/mremap
* fail gracefully when no instances found
* no-map required in DT bindings to ensure mem region not treated as RAM
Changes since v5:
* replaced 'additionalProperties' with 'unevaluatedProperties' in DT YAML
Changes since v4:
* registered compatible in 'reserved_mem_matches'
* removed unnecessary DT node, only reserved-memory
* fixed typos in comments
Changes since v3:
* align with semantics of read/write
* fix kerneldoc warnings
* fix printf format warnings
Changes since v2:
* renamed from 'dice' to 'open-dice'
* replaced ioctls with read/write
* replaced memzero_explicit with memset
* allowed multiple instances
* expanded Kconfig description
Changes since v1:
* converted to miscdevice
* all mappings now write-combine to simplify semantics
* removed atomic state, any attempt at exclusive access
* simplified wipe, applied on ioctl, not on release
* fixed ioctl return value
David Brazdil (2):
dt-bindings: reserved-memory: Open Profile for DICE
misc: open-dice: Add driver to expose DICE data to userspace
.../reserved-memory/google,open-dice.yaml | 46 ++++
drivers/misc/Kconfig | 12 +
drivers/misc/Makefile | 1 +
drivers/misc/open-dice.c | 208 ++++++++++++++++++
drivers/of/platform.c | 1 +
5 files changed, 268 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reserved-memory/google,open-dice.yaml
create mode 100644 drivers/misc/open-dice.c
--
2.35.0.rc0.227.g00780c9af4-goog
next reply other threads:[~2022-01-26 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 23:12 David Brazdil [this message]
2022-01-26 23:12 ` [PATCH v7 1/2] dt-bindings: reserved-memory: Open Profile for DICE David Brazdil
2022-01-26 23:19 ` David Brazdil
2022-02-01 23:39 ` Rob Herring
2022-01-26 23:12 ` [PATCH v7 2/2] misc: open-dice: Add driver to expose DICE data to userspace David Brazdil
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=20220126231237.529308-1-dbrazdil@google.com \
--to=dbrazdil@google.com \
--cc=arnd@arndb.de \
--cc=ascull@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wedsonaf@google.com \
--cc=will@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).