diff options
author | Linus Torvalds | 2019-04-15 16:48:51 -0700 |
---|---|---|
committer | Linus Torvalds | 2019-04-15 16:48:51 -0700 |
commit | 618d919cae2fcaadc752f27ddac8b939da8b441a (patch) | |
tree | def6e581d1787e1cd2f758c7e1c5917ac4441dba /tools/lib | |
parent | 5512320c9f6f2acd7972c05400473c2338325339 (diff) | |
parent | 2170a0d53bee1a6c1a4ebd042f99d85aafc6c0ea (diff) |
Merge tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull libnvdimm fixes from Dan Williams:
"I debated holding this back for the v5.2 merge window due to the size
of the "zero-key" changes, but affected users would benefit from
having the fixes sooner. It did not make sense to change the zero-key
semantic in isolation for the "secure-erase" command, but instead
include it for all security commands.
The short background on the need for these changes is that some NVDIMM
platforms enable security with a default zero-key rather than let the
OS specify the initial key. This makes the security enabling that
landed in v5.0 unusable for some users.
Summary:
- Compatibility fix for nvdimm-security implementations with a
default zero-key.
- Miscellaneous small fixes for out-of-bound accesses, cleanup after
initialization failures, and missing debug messages"
* tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm:
tools/testing/nvdimm: Retain security state after overwrite
libnvdimm/pmem: fix a possible OOB access when read and write pmem
libnvdimm/security, acpi/nfit: unify zero-key for all security commands
libnvdimm/security: provide fix for secure-erase to use zero-key
libnvdimm/btt: Fix a kmemdup failure check
libnvdimm/namespace: Fix a potential NULL pointer dereference
acpi/nfit: Always dump _DSM output payload
Diffstat (limited to 'tools/lib')
0 files changed, 0 insertions, 0 deletions