On Tue, Apr 26, 2016 at 02:33:49PM -0700, Rafael Antognolli wrote:
> On Mon, Apr 25, 2016 at 08:29:22PM -0700, Elliott, Robert (Persistent Memory)
> wrote:
> >
> >
> > > -Original Message-
> > > From: linux-block-ow...@vger.kernel.org [mailto:linux-bl
April 25, 2016 3:24 AM
> > To: Rafael Antognolli
> > Cc: linux-n...@lists.infradead.org; linux-kernel@vger.kernel.org;
> > linux-bl...@vger.kernel.org
> > Subject: Re: [PATCH 0/2] Add Opal unlock support to NVMe.
> >
> > On Fri, Apr 22, 2016 at 04:12:10PM -0700, Rafa
locking range (if a password for it is saved) during PM
resume.
Signed-off-by: Rafael Antognolli
---
drivers/nvme/host/core.c| 9 +
include/uapi/linux/nvme_ioctl.h | 7 +++
2 files changed, 16 insertions(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index
d 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
ot;unlock range"
commands (from the OPAL spec):
* STARTSESSION
* SET(locking range, readwrite)
* ENDSESSION
Signed-off-by: Rafael Antognolli
---
drivers/nvme/host/Kconfig |7 +
drivers/nvme/host/Makefile|1 +
drivers/nvme/host/opal.c | 1270
On Thu, Feb 09, 2017 at 10:20:01AM -0700, Scott Bauer wrote:
> When CONFIG_KASAN is enabled, compilation fails:
>
> block/sed-opal.c: In function 'sed_ioctl':
> block/sed-opal.c:2447:1: error: the frame size of 2256 bytes is larger than
> 2048 bytes [-Werror=frame-larger-than=]
>
> Moved all the
6 matches
Mail list logo