Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel@jbeekman.nl (Jethro Beekman)
Subject: [PATCH 0/2] Add Opal unlock support to NVMe.
Date: Mon, 20 Jun 2016 11:24:24 -0700	[thread overview]
Message-ID: <576834D8.9050101@jbeekman.nl> (raw)
In-Reply-To: <20160426213349.GA17078@intel.com>

On Tue Apr 26 14:33:49 PDT 2016, Rafael Antognolli wrote:
>> > 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.
>> 
>> NVDIMMs would benefit from that as well.
> 
> Yes, I can definitely change it to be that generic.

Hi Rafael,

Did you make any progress making this generic? I ran into the same thing for ATA
security:

  http://lists.infradead.org/pipermail/linux-nvme/2016-June/005116.html

I think the kernel would benefit from some sort of generic drive security state
tracker. Would you like to join forces on this?

Jethro Beekman

      parent reply	other threads:[~2016-06-20 18:24 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
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 [this message]

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=576834D8.9050101@jbeekman.nl \
    --to=kernel@jbeekman.nl \
    /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