From: Dave Jiang <dave.jiang@intel.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: alison.schofield@intel.com, keescook@chromium.org,
linux-nvdimm@lists.01.org, dhowells@redhat.com,
keyrings@vger.kernel.org
Subject: Re: [PATCH v5 00/12] Adding security support for nvdimm
Date: Tue, 17 Jul 2018 16:37:14 -0700 [thread overview]
Message-ID: <2654dc07-a1ae-e8ab-cb97-bb2846755559@intel.com> (raw)
In-Reply-To: <20180717232626.GA176997@gmail.com>
On 07/17/2018 04:26 PM, Eric Biggers wrote:
> On Tue, Jul 17, 2018 at 01:54:04PM -0700, Dave Jiang wrote:
>> The following series implements security support for nvdimm. Mostly adding
>> new security DSM support from the Intel NVDIMM DSM spec v1.7, but also
>> adding generic support libnvdimm for other vendors. The most important
>> security features are unlocking locked nvdimms, and updating/setting security
>> passphrase to nvdimms.
>>
>> Security folks, thanks in advance for taking a look at my key management
>> implementation and making sure that I'm doing something sane. Mainly you'll
>> want to review patches 2, 4, 5, and 6 as most relevant ones that need scrutiny.
>>
>> v5:
>> - Moved dimm_id initialization (Dan)
>> - Added a key_put_sync() in order to run key_gc_work and cleanup old key. (Dan)
>> - Added check to block security state changes while DIMM is active. (Dan)
>>
>> v4:
>> - flip payload layout for update passphrase to make it easier on userland.
>>
>> v3:
>> - Set x86 wrappers for x86 only bits. (Dan)
>> - Fixed up some verbiage in commit headers.
>> - Put in usage of sysfs_streq() for sysfs inputs.
>> - 0-day build fixes for non-x86 archs.
>>
>> v2:
>> - Move inclusion of intel.h to relevant source files and not in nfit.h. (Dan)
>> - Moved security ring relevant code to dimm_devs.c. (Dan)
>> - Added dimm_id to nfit_mem to avoid recreate per sysfs show call. (Dan)
>> - Added routine to return security_ops based on family supplied. (Dan)
>> - Added nvdimm_key_data struct to wrap raw passphrase string. (Dan)
>> - Allocate firmware package on stack. (Dan)
>> - Added missing frozen state detection when retrieving security state.
>>
>> ---
>>
>> Dave Jiang (12):
>> nfit: add support for Intel DSM 1.7 commands
>> libnvdimm: create keyring to store security keys
>> nfit/libnvdimm: store dimm id as a member to struct nvdimm
>> nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs
>> keys: add call key_put_sync() to flush key_gc_work when doing a key_put().
>> nfit/libnvdimm: add set passphrase support for Intel nvdimms
>> nfit/libnvdimm: add disable passphrase support to Intel nvdimm.
>> nfit/libnvdimm: add freeze security support to Intel nvdimm
>> nfit/libnvdimm: add support for issue secure erase DSM to Intel nvdimm
>> nfit_test: add context to dimm_dev for nfit_test
>> nfit_test: add test support for Intel nvdimm security DSMs
>> libnvdimm: add documentation for nvdimm security support
>>
>>
>> Documentation/nvdimm/security | 70 ++++++
>> drivers/acpi/nfit/Makefile | 1
>> drivers/acpi/nfit/core.c | 58 ++++-
>> drivers/acpi/nfit/intel.c | 366 ++++++++++++++++++++++++++++++++
>> drivers/acpi/nfit/intel.h | 83 +++++++
>> drivers/acpi/nfit/nfit.h | 20 ++
>> drivers/nvdimm/bus.c | 2
>> drivers/nvdimm/core.c | 7 +
>> drivers/nvdimm/dimm.c | 7 +
>> drivers/nvdimm/dimm_devs.c | 430 ++++++++++++++++++++++++++++++++++++++
>> drivers/nvdimm/nd-core.h | 4
>> drivers/nvdimm/nd.h | 2
>> include/linux/key.h | 1
>> include/linux/libnvdimm.h | 41 +++-
>> security/keys/key.c | 35 +++
>> tools/testing/nvdimm/Kbuild | 1
>> tools/testing/nvdimm/test/nfit.c | 227 +++++++++++++++++++-
>> 17 files changed, 1315 insertions(+), 40 deletions(-)
>> create mode 100644 Documentation/nvdimm/security
>> create mode 100644 drivers/acpi/nfit/intel.c
>> create mode 100644 drivers/acpi/nfit/intel.h
>>
>
> Which git tree does this series apply to? I tried upstream, linux-next, and
> linux-block/for-next, but in all cases patch 4 doesn't apply:
>
> Applying: nfit: add support for Intel DSM 1.7 commands
> Applying: libnvdimm: create keyring to store security keys
> Applying: nfit/libnvdimm: store dimm id as a member to struct nvdimm
> Applying: nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs
> error: sha1 information is lacking or useless (drivers/acpi/nfit/core.c).
> error: could not build fake ancestor
> Patch failed at 0004 nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs
>
You can grab it here
https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git/log/?h=nvdimm-security
I based my stuff on top of couple patches from Dan that has to do with
locked DIMM label reading. And those are queued for 4.19.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-07-17 23:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 20:54 [PATCH v5 00/12] Adding security support for nvdimm Dave Jiang
2018-07-17 20:54 ` [PATCH v5 01/12] nfit: add support for Intel DSM 1.7 commands Dave Jiang
2018-07-18 17:02 ` Elliott, Robert (Persistent Memory)
2018-07-17 20:54 ` [PATCH v5 02/12] libnvdimm: create keyring to store security keys Dave Jiang
2018-07-17 23:56 ` Eric Biggers
2018-07-17 20:54 ` [PATCH v5 03/12] nfit/libnvdimm: store dimm id as a member to struct nvdimm Dave Jiang
2018-07-18 15:40 ` Elliott, Robert (Persistent Memory)
2018-07-18 15:49 ` Dave Jiang
2018-07-17 20:54 ` [PATCH v5 04/12] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs Dave Jiang
2018-07-18 0:00 ` Eric Biggers
2018-07-17 20:54 ` [PATCH v5 05/12] keys: add call key_put_sync() to flush key_gc_work when doing a key_put() Dave Jiang
2018-07-17 23:53 ` Eric Biggers
2018-07-17 23:58 ` Dave Jiang
2018-07-17 20:54 ` [PATCH v5 06/12] nfit/libnvdimm: add set passphrase support for Intel nvdimms Dave Jiang
2018-07-17 20:54 ` [PATCH v5 07/12] nfit/libnvdimm: add disable passphrase support to Intel nvdimm Dave Jiang
2018-07-17 20:54 ` [PATCH v5 08/12] nfit/libnvdimm: add freeze security " Dave Jiang
2018-07-17 20:54 ` [PATCH v5 09/12] nfit/libnvdimm: add support for issue secure erase DSM " Dave Jiang
2018-07-18 17:27 ` Elliott, Robert (Persistent Memory)
2018-07-18 17:41 ` Dave Jiang
2018-07-19 1:43 ` Elliott, Robert (Persistent Memory)
2018-07-19 6:09 ` Li, Juston
2018-07-19 20:06 ` Dave Jiang
2018-07-17 20:55 ` [PATCH v5 10/12] nfit_test: add context to dimm_dev for nfit_test Dave Jiang
2018-07-17 20:55 ` [PATCH v5 11/12] nfit_test: add test support for Intel nvdimm security DSMs Dave Jiang
2018-07-17 20:55 ` [PATCH v5 12/12] libnvdimm: add documentation for nvdimm security support Dave Jiang
2018-07-17 23:26 ` [PATCH v5 00/12] Adding security support for nvdimm Eric Biggers
2018-07-17 23:37 ` Dave Jiang [this message]
2018-07-18 10:40 ` [PATCH v5 05/12] keys: add call key_put_sync() to flush key_gc_work when doing a key_put() David Howells
2018-07-18 10:50 ` [PATCH v5 02/12] libnvdimm: create keyring to store security keys David Howells
2018-07-18 19:40 ` Dave Jiang
2018-07-18 20:38 ` David Howells
2018-07-18 11:14 ` [PATCH v5 06/12] nfit/libnvdimm: add set passphrase support for Intel nvdimms David Howells
2018-07-18 16:05 ` Dave Jiang
2018-07-18 19:47 ` Dave Jiang
2018-07-18 20:41 ` David Howells
2018-07-18 20:47 ` Dave Jiang
2018-07-19 0:28 ` Dave Jiang
2018-07-19 8:22 ` David Howells
2018-07-19 21:28 ` Dave Jiang
2018-07-20 0:04 ` Dave Jiang
2018-07-20 15:40 ` David Howells
2018-07-20 16:40 ` Dave Jiang
2018-08-02 11:07 ` David Howells
2018-07-18 11:17 ` [PATCH v5 05/12] keys: add call key_put_sync() to flush key_gc_work when doing a key_put() David Howells
2018-07-18 11:20 ` [PATCH v5 06/12] nfit/libnvdimm: add set passphrase support for Intel nvdimms David Howells
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=2654dc07-a1ae-e8ab-cb97-bb2846755559@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dhowells@redhat.com \
--cc=ebiggers3@gmail.com \
--cc=keescook@chromium.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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).