Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 0/2] Add Opal unlock support to NVMe.
Date: Mon, 25 Apr 2016 10:39:05 +0200	[thread overview]
Message-ID: <571DD7A9.406@suse.de> (raw)
In-Reply-To: <20160425082408.GA13629@infradead.org>

On 04/25/2016 10:24 AM, Christoph Hellwig wrote:
> On Fri, Apr 22, 2016@04:12:10PM -0700, Rafael Antognolli wrote:
>> 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).
> 
> I think the OPAL code should be a generic library outside the NVMe
> code so that we can use it for SATA and SAS as well, just with a little
> glue code for the Security Send / Receive commands to wire it up to
> NVMe.
> 
Fully agree. Having generic OPAL support would be a major benefit.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare at suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: F. Imend?rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG N?rnberg)

  reply	other threads:[~2016-04-25  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 23:12 [PATCH 0/2] Add Opal unlock support to NVMe Rafael Antognolli
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-25  8:39   ` Hannes Reinecke [this message]
2016-04-26  3:29   ` Elliott, Robert (Persistent Memory)
2016-04-26 21:33     ` Rafael Antognolli
2016-05-18 23:54       ` Rafael Antognolli
2016-06-20 18:24       ` Jethro Beekman

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=571DD7A9.406@suse.de \
    --to=hare@suse.de \
    /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