linux-stable.git/tools/testing/nvdimm, branch v4.13.2

tools/testing/nvdimm: fix nfit_test buffer overflow

2017-06-15T21:31:41+00:00

The root cause of panic is the num_pm of nfit_test1 is wrong.
Though 1 is specified for num_pm at nfit_test_init(), it must be 2,
because nfit_test1->spa_set[] array has 2 elements.

Since the array is smaller than expected, the driver breaks other area.
(it is often the link list of devres).

As a result, panic occurs like the following example.

    CPU: 4 PID: 2233 Comm: lt-libndctl Tainted: G           O    4.12.0-rc1+ #12
    RIP: 0010:__list_del_entry_valid+0x6c/0xa0
    Call Trace:
     release_nodes+0x76/0x260
     devres_release_all+0x3c/0x50
     device_release_driver_internal+0x159/0x200
     device_release_driver+0x12/0x20
     bus_remove_device+0xfd/0x170
     device_del+0x1e8/0x330
     platform_device_del+0x28/0x90
     platform_device_unregister+0x12/0x30
     nfit_test_exit+0x2a/0x93b [nfit_test]

Cc: 
Signed-off-by: Yasunori Goto 
Signed-off-by: Dan Williams

ACPI: Switch to use generic guid_t in acpi_evaluate_dsm()

2017-06-07T10:20:49+00:00

acpi_evaluate_dsm() and friends take a pointer to a raw buffer of 16
bytes. Instead we convert them to use guid_t type. At the same time we
convert current users.

acpi_str_to_uuid() becomes useless after the conversion and it's safe to
get rid of it.

Acked-by: Rafael J. Wysocki 
Cc: Borislav Petkov 
Acked-by: Dan Williams 
Cc: Amir Goldstein 
Reviewed-by: Jarkko Sakkinen 
Reviewed-by: Jani Nikula 
Acked-by: Jani Nikula 
Cc: Ben Skeggs 
Acked-by: Benjamin Tissoires 
Acked-by: Joerg Roedel 
Acked-by: Adrian Hunter 
Cc: Yisen Zhuang 
Acked-by: Bjorn Helgaas 
Acked-by: Felipe Balbi 
Acked-by: Mathias Nyman 
Reviewed-by: Heikki Krogerus 
Acked-by: Mark Brown 
Signed-off-by: Andy Shevchenko 
Signed-off-by: Christoph Hellwig

Merge branch 'for-4.12/dax' into libnvdimm-for-next

2017-05-05T06:38:43+00:00

pmem: add dax_operations support

2017-04-19T22:14:35+00:00

Setup a dax_device to have the same lifetime as the pmem block device
and add a ->direct_access() method that is equivalent to
pmem_direct_access(). Once fs/dax.c has been converted to use
dax_operations the old pmem_direct_access() will be removed.

Signed-off-by: Dan Williams

acpi, nfit: fix module unload vs workqueue shutdown race

2017-04-18T17:55:37+00:00

The workqueue may still be running when the devres callbacks start
firing to deallocate an acpi_nfit_desc instance. Stop and flush the
workqueue before letting any other devres de-allocations proceed.

Reported-by: Linda Knippers 
Signed-off-by: Dan Williams

tools/testing/nvdimm: fix nfit_test shutdown crash

2017-04-18T17:26:09+00:00

Keep the nfit_test instances alive until after nfit_test_teardown(), as
we may be doing resource lookups until the final un-registrations have
completed. This fixes crashes of the form.

 BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
 IP: __release_resource+0x12/0x90
 Call Trace:
  remove_resource+0x23/0x40
  __wrap_remove_resource+0x29/0x30 [nfit_test_iomap]
  acpi_nfit_remove_resource+0xe/0x10 [nfit]
  devm_action_release+0xf/0x20
  release_nodes+0x16d/0x2b0
  devres_release_all+0x3c/0x60
  device_release+0x21/0x90
  kobject_release+0x6a/0x170
  kobject_put+0x2f/0x60
  put_device+0x17/0x20
  platform_device_unregister+0x20/0x30
  nfit_test_exit+0x36/0x960 [nfit_test]

Reported-by: Linda Knippers 
Signed-off-by: Dan Williams

tools/testing/nvdimm: test acpi 6.1 health state flags

2017-04-17T19:34:17+00:00

Add a simulated dimm with an ACPI_NFIT_MEM_MAP_FAILED indication, and
set the ACPI_NFIT_MEM_HEALTH_ENABLED flag on all the dimms where
nfit_test simulates health events, but spread it out over several
redundant memdev entries to test that the nfit driver coalesces all the
flags.

Signed-off-by: Dan Williams

dax: refactor dax-fs into a generic provider of 'struct dax_device' instances

2017-04-13T04:59:14+00:00

We want dax capable drivers to be able to publish a set of dax
operations [1]. However, we do not want to further abuse block_devices
to advertise these operations. Instead we will attach these operations
to a dax device and add a lookup mechanism to go from block device path
to a dax device. A dax capable driver like pmem or brd is responsible
for registering a dax device, alongside a block device, and then a dax
capable filesystem is responsible for retrieving the dax device by path
name if it wants to call dax_operations.

For now, we refactor the dax pseudo-fs to be a generic facility, rather
than an implementation detail, of the device-dax use case. Where a "dax
device" is just an inode + dax infrastructure, and "Device DAX" is a
mapping service layered on top of that base 'struct dax_device'.
"Filesystem DAX" is then a mapping service that layers a filesystem on
top of that same base device. Filesystem DAX is associated with a
block_device for now, but perhaps directly to a dax device in the
future, or for new pmem-only filesystems.

[1]: https://lkml.org/lkml/2017/1/19/880

Suggested-by: Christoph Hellwig 
Signed-off-by: Dan Williams

device-dax, tools/testing/nvdimm: enable device-dax with mock resources

2017-04-13T04:56:43+00:00

Provide a replacement pgoff_to_phys() that translates an nfit_test
resource (allocated by vmalloc()) to a pfn.

Signed-off-by: Dave Jiang 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Dan Williams

tools/testing/nvdimm: make iset cookie predictable

2017-03-01T08:09:51+00:00

For testing changes to the iset cookie algorithm we need a value that is
constant from run-to-run.

Stop including dynamic data in the emulated region_offset values. Also,
pick values that sort in a different order depending on whether the
comparison is a memcmp() of two 8-byte arrays or subtraction of two
64-bit values.

Signed-off-by: Dan Williams