kernel/linux.git/tools/testing/nvdimm, branch v4.17.5Linux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=v4.17.52018-04-16T15:18:51+00:00tools/testing/nvdimm: enable labels for nfit_test.1 dimms2018-04-16T15:18:51+00:00Dan Williamsdan.j.williams@intel.com2018-04-09T21:29:33+00:00urn:sha1:9484e12d7999a3c82d8732b60c0149f038bdd985
Enable test cases for the kernel's fallback to label-less mode.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
tools/testing/nvdimm: fix missing newline in nfit_test_dimm 'handle' attribute2018-04-16T15:18:51+00:00Dan Williamsdan.j.williams@intel.com2018-04-10T21:23:47+00:00urn:sha1:19357a685e870eeb825cbb7fd3104082ab041987
Sysfs userspace tooling generally expects the kernel to emit a newlines
when reading sysfs attributes.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
tools/testing/nvdimm: support nfit_test_dimm attributes under nfit_test.12018-04-16T15:18:51+00:00Dan Williamsdan.j.williams@intel.com2018-04-09T23:38:01+00:00urn:sha1:718fda67d2f69cc6074b4b6a740a6e4aacd44eff
The nfit_test.1 bus provides a pmem topology without blk-aperture
enabling, so it presents different failure modes for label space
handling. Allow custom DSM command error injection.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>tools/testing/nvdimm: allow custom error code injection2018-04-16T15:18:51+00:00Dan Williamsdan.j.williams@intel.com2018-04-09T20:56:43+00:00urn:sha1:55c72ab62e47fc584131901baddb2752e949ebcd
Given that libnvdimm driver stack takes specific actions on DIMM command
error codes like -EACCES, provide a facility to inject custom failures.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
libnvdimm, testing: update the default smart ctrl_temperature2018-04-06T03:12:00+00:00Vishal Vermavishal.l.verma@intel.com2018-02-08T21:24:05+00:00urn:sha1:f6adcca02ca26577692a1f2ee892c134b076b339
The default value for smart ctrl_temperature was the same as the
threshold for ctrl_temperature. As a result, any arbitrary smart
injection to the nfit_test dimm could cause this alarm to trigger
and cause an acpi notification. Drop the default value to below the
threshold, so that unrelated injections don't trigger notifications.
Cc: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
libnvdimm, testing: Add emulation for smart injection commands2018-04-06T03:11:19+00:00Vishal Vermavishal.l.verma@intel.com2018-02-08T21:24:04+00:00urn:sha1:4cf260fc409c73f6e40b3e8061a0cb925703d7ee
Add support for the smart injection command in the nvdimm unit test
framework. This allows for directly injecting to smart fields and flags
that are supported in the injection command. If the injected values are
past the threshold, then an acpi notification is also triggered.
Cc: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
nfit_test: prevent parsing error of nfit_test.02018-03-06T19:06:41+00:00Ross Zwislerross.zwisler@linux.intel.com2018-02-27T17:29:52+00:00urn:sha1:1526f9e2ac1df62106c15a18fd6895258c579c90
When you load nfit_test you currently see the following error in dmesg:
nfit_test nfit_test.0: found a zero length table '0' parsing nfit
This happens because when we parse the nfit_test.0 table via
acpi_nfit_init(), we specify a size of nfit_test->nfit_size. For the first
pass through nfit_test.0 where (t->setup_hotplug == 0) this is the size of
the entire buffer we allocated, including space for the hot plug
structures, not the size that we've actually filled in.
Fix this by only trying to parse the size of the structures that we've
filled in.
Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
nfit_test: fix buffer overrun, add sanity check2018-03-06T19:05:37+00:00Ross Zwislerross.zwisler@linux.intel.com2018-02-27T17:29:51+00:00urn:sha1:9741a559971856fca61a83840b558b4f94500d89
It turns out that we were overrunning the 'nfit_buf' buffer in
nfit_test0_setup() in the (t->setup_hotplug == 1) case because we failed to
correctly account for all of the acpi_nfit_memory_map structures.
Fix the structure count which will increase the allocation size of
'nfit_buf' in nfit_test0_alloc(). Also add some WARN_ON()s to
nfit_test0_setup() and nfit_test1_setup() to catch future issues where the
size of the buffer doesn't match the amount of data we're writing.
Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
nfit_test: improve structure offset handling2018-03-06T19:05:08+00:00Ross Zwislerross.zwisler@linux.intel.com2018-02-27T17:29:50+00:00urn:sha1:d7d8464dcc27dfc9d0d23c7924b2e6f4bb16c6c2
In nfit_test0_setup() and nfit_test1_setup() we keep an 'offset' value
which we use to calculate where in our 'nfit_buf' we will place our next
structure. The handling of 'offset' and the calculation of the placement
of the next structure is a bit inconsistent, though. We don't update
'offset' after we insert each structure, sometimes causing us to update it
for multiple structures' sizes at once. When calculating the position of
the next structure we aren't always able to just use 'offset', but
sometimes have to add in other structure sizes as well.
Fix this by updating 'offset' after each structure insertion in a
consistent way, allowing us to always calculate the position of the next
structure to be inserted by just using 'nfit_buf + offset'.
Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Merge branch 'for-4.16/nfit' into libnvdimm-for-next2018-02-03T07:26:26+00:00Ross Zwislerross.zwisler@linux.intel.com2018-02-03T07:26:26+00:00urn:sha1:ee95f4059a833839bf52972191b2d4c3d3cec552