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

tools/testing/nvdimm: fix SIGTERM vs hotplug crash

2016-09-07T06:34:43+00:00

commit d8d378fa1a0c98ecb50ca52c9bf3bc14e25aa2d2 upstream.

The unit tests crash when hotplug races the previous probe. This race
requires that the loading of the nfit_test module be terminated with
SIGTERM, and the module to be unloaded while the ars scan is still
running.

In contrast to the normal nfit driver, the unit test calls
acpi_nfit_init() twice to simulate hotplug, whereas the nominal case
goes through the acpi_nfit_notify() event handler.  The
acpi_nfit_notify() path is careful to flush the previous region
registration before servicing the hotplug event. The unit test was
missing this guarantee.

 BUG: unable to handle kernel NULL pointer dereference at           (null)
 IP: [] pwq_activate_delayed_work+0x47/0x170
 [..]
 Call Trace:
  [] pwq_dec_nr_in_flight+0x66/0xa0
  [] process_one_work+0x2d0/0x680
  [] ? process_one_work+0x171/0x680
  [] worker_thread+0x4e/0x480
  [] ? process_one_work+0x680/0x680
  [] ? process_one_work+0x680/0x680
  [] kthread+0xf3/0x110
  [] ret_from_fork+0x1f/0x40
  [] ? kthread_create_on_node+0x230/0x230

Signed-off-by: Dan Williams 
Signed-off-by: Greg Kroah-Hartman

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

2016-05-21T19:33:04+00:00

/dev/dax, pmem: direct access to persistent memory

2016-05-21T05:02:53+00:00

Device DAX is the device-centric analogue of Filesystem DAX
(CONFIG_FS_DAX).  It allows memory ranges to be allocated and mapped
without need of an intervening file system.  Device DAX is strict,
precise and predictable.  Specifically this interface:

1/ Guarantees fault granularity with respect to a given page size (pte,
pmd, or pud) set at configuration time.

2/ Enforces deterministic behavior by being strict about what fault
scenarios are supported.

For example, by forcing MADV_DONTFORK semantics and omitting MAP_PRIVATE
support device-dax guarantees that a mapping always behaves/performs the
same once established.  It is the "what you see is what you get" access
mechanism to differentiated memory vs filesystem DAX which has
filesystem specific implementation semantics.

Persistent memory is the first target, but the mechanism is also
targeted for exclusive allocations of performance differentiated memory
ranges.

This commit is limited to the base device driver infrastructure to
associate a dax device with pmem range.

Cc: Jeff Moyer 
Cc: Christoph Hellwig 
Cc: Andrew Morton 
Cc: Dave Hansen 
Cc: Ross Zwisler 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Dan Williams

Merge branch 'for-4.7/dsm' into libnvdimm-for-next

2016-05-18T17:06:59+00:00

Merge branch 'for-4.7/libnvdimm' into libnvdimm-for-next

2016-05-18T17:06:48+00:00

libnvdimm, dax: introduce device-dax infrastructure

2016-05-09T22:35:42+00:00

Device DAX is the device-centric analogue of Filesystem DAX
(CONFIG_FS_DAX).  It allows persistent memory ranges to be allocated and
mapped without need of an intervening file system.  This initial
infrastructure arranges for a libnvdimm pfn-device to be represented as
a different device-type so that it can be attached to a driver other
than the pmem driver.

Signed-off-by: Dan Williams

tools/testing/nvdimm: ND_CMD_CALL support

2016-05-06T02:02:45+00:00

Enable nfit_test to use nd_cmd_pkg marshaling.

Signed-off-by: Dan Williams

nfit, libnvdimm: clarify "commands" vs "_DSMs"

2016-04-28T23:23:16+00:00

Clarify the distinction between "commands", the ioctls userspace calls
to request the kernel take some action on a given dimm device, and
"_DSMs", the actual function numbers used in the firmware interface to
the DIMM.  _DSMs are ACPI specific whereas commands are Linux kernel
generic.

This is in preparation for breaking the 1:1 implicit relationship
between the kernel ioctl number space and the firmware specific function
numbers.

Cc: Jerry Hoemann 
Cc: Christoph Hellwig 
Signed-off-by: Dan Williams

libnvdimm, pmem, pfn: make pmem_rw_bytes generic and refactor pfn setup

2016-04-22T19:26:23+00:00

In preparation for providing an alternative (to block device) access
mechanism to persistent memory, convert pmem_rw_bytes() to
nsio_rw_bytes().  This allows ->rw_bytes() functionality without
requiring a 'struct pmem_device' to be instantiated.

In other words, when ->rw_bytes() is in use i/o is driven through
'struct nd_namespace_io', otherwise it is driven through 'struct
pmem_device' and the block layer.  This consolidates the disjoint calls
to devm_exit_badblocks() and devm_memunmap() into a common
devm_nsio_disable() and cleans up the init path to use a unified
pmem_attach_disk() implementation.

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

libnvdimm, test: add mock SMART data payload

2016-04-11T18:11:14+00:00

Provide simulated SMART data to enable the ndctl implementation of SMART
data retrieval and parsing.

The payload is defined here, "Section 4.1 SMART and Health Info
(Function Index 1)":

    http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf

Signed-off-by: Dan Williams