diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2019-01-09 02:34:52 +0300 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2019-01-09 09:06:09 +0300 |
| commit | 1cb95e072ede5e3d6a54eefd520db21b45985896 (patch) | |
| tree | 3cb1ea431423fc4e0102989fc7a4de76edb309e4 /fs/devpts | |
| parent | ccb7f15a8a3c0c7a35389e4c8e083c424b4df79d (diff) | |
| download | linux-1cb95e072ede5e3d6a54eefd520db21b45985896.tar.xz | |
libnvdimm/dimm: Fix security capability detection for non-Intel NVDIMMs
Kees reports a crash with the following signature...
RIP: 0010:nvdimm_visible+0x79/0x80
[..]
Call Trace:
internal_create_group+0xf4/0x380
sysfs_create_groups+0x46/0xb0
device_add+0x331/0x680
nd_async_device_register+0x15/0x60
async_run_entry_fn+0x38/0x100
...when starting a QEMU environment with "label-less" DIMM. Without
labels QEMU does not publish any DSM methods. Without defined methods
the NVDIMM_FAMILY type is not established and the nfit driver will skip
registering security operations.
In that case the security state should be initialized to a negative
value in __nvdimm_create() and nvdimm_visible() should skip
interrogating the specific ops. However, since 'enum
nvdimm_security_state' was only defined to contain positive values the
"if (nvdimm->sec.state < 0)" check always fails.
Define a negative error state to allow negative state values to be
handled as expected.
Fixes: f2989396553a ("acpi/nfit, libnvdimm: Introduce nvdimm_security_ops")
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Reported-by: Kees Cook <keescook@chromium.org>
Tested-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'fs/devpts')
0 files changed, 0 insertions, 0 deletions