From: Rafael Antognolli <rafael.antognolli@intel.com>
To: linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Rafael Antognolli <rafael.antognolli@intel.com>
Subject: [PATCH 0/2] Add Opal unlock support to NVMe.
Date: Fri, 22 Apr 2016 16:12:10 -0700 [thread overview]
Message-ID: <1461366732-31779-1-git-send-email-rafael.antognolli@intel.com> (raw)
This patch series implement a small set of the Opal protocol for self
encrypting devices. It's implemented only what is needed for saving a password
and unlocking a given "locking range". The password is saved on the driver and
replayed back to the device on resume from suspend to RAM. It is specifically
supporting the single user mode.
It is not planned to implement the full Opal protocol (at least not for now).
Rafael Antognolli (2):
Add optane OPAL unlocking code.
NVMe: Add ioctls to save and unlock an Opal locking range.
drivers/nvme/host/Kconfig | 7 +
drivers/nvme/host/Makefile | 1 +
drivers/nvme/host/core.c | 9 +
drivers/nvme/host/opal.c | 1270 +++++++++++++++++++++++++++++++++++++
drivers/nvme/host/opal.h | 73 +++
drivers/nvme/host/opal_internal.h | 501 +++++++++++++++
include/uapi/linux/nvme_ioctl.h | 7 +
7 files changed, 1868 insertions(+)
create mode 100644 drivers/nvme/host/opal.c
create mode 100644 drivers/nvme/host/opal.h
create mode 100644 drivers/nvme/host/opal_internal.h
--
1.9.1
next reply other threads:[~2016-04-22 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 23:12 Rafael Antognolli [this message]
2016-04-22 23:12 ` [PATCH 1/2] Add optane OPAL unlocking code Rafael Antognolli
2016-04-22 23:12 ` [PATCH 2/2] NVMe: Add ioctls to save and unlock an Opal locking range Rafael Antognolli
2016-04-25 8:24 ` [PATCH 0/2] Add Opal unlock support to NVMe Christoph Hellwig
2016-04-26 3:29 ` Elliott, Robert (Persistent Memory)
2016-04-26 21:33 ` Rafael Antognolli
2016-05-18 23:54 ` Rafael Antognolli
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=1461366732-31779-1-git-send-email-rafael.antognolli@intel.com \
--to=rafael.antognolli@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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
all inboxes | Powered by JetHome®