linux-toradex.git/drivers/md/dm-writecache.c, branch v5.0-rc3

dm writecache: fix typo in error msg for creating writecache_flush_thread

2018-12-18T14:02:26+00:00

The error msg should be "flush thread" instead of "endio thread"
for writecache_flush_thread.

Signed-off-by: Shenghui Wang 
Signed-off-by: Mike Snitzer

dm writecache: remove disabled code in memory_entry()

2018-10-22T14:59:52+00:00

This dead branch was missed during review.  It only makes memory_entry()
more inefficient due to needless call to is_power_of_2(), etc.

Reported-by: shenghui 
Signed-off-by: Mike Snitzer

Merge tag 'libnvdimm-for-4.19_misc' of gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm

2018-08-26T01:13:10+00:00

Pull libnvdimm updates from Dave Jiang:
 "Collection of misc libnvdimm patches for 4.19 submission:

   - Adding support to read locked nvdimm capacity.

   - Change test code to make DSM failure code injection an override.

   - Add support for calculate maximum contiguous area for namespace.

   - Add support for queueing a short ARS when there is on going ARS for
     nvdimm.

   - Allow NULL to be passed in to ->direct_access() for kaddr and pfn
     params.

   - Improve smart injection support for nvdimm emulation testing.

   - Fix test code that supports for emulating controller temperature.

   - Fix hang on error before devm_memremap_pages()

   - Fix a bug that causes user memory corruption when data returned to
     user for ars_status.

   - Maintainer updates for Ross Zwisler emails and adding Jan Kara to
     fsdax"

* tag 'libnvdimm-for-4.19_misc' of gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm:
  libnvdimm: fix ars_status output length calculation
  device-dax: avoid hang on error before devm_memremap_pages()
  tools/testing/nvdimm: improve emulation of smart injection
  filesystem-dax: Do not request kaddr and pfn when not required
  md/dm-writecache: Don't request pointer dummy_addr when not required
  dax/super: Do not request a pointer kaddr when not required
  tools/testing/nvdimm: kaddr and pfn can be NULL to ->direct_access()
  s390, dcssblk: kaddr and pfn can be NULL to ->direct_access()
  libnvdimm, pmem: kaddr and pfn can be NULL to ->direct_access()
  acpi/nfit: queue issuing of ars when an uc error notification comes in
  libnvdimm: Export max available extent
  libnvdimm: Use max contiguous area for namespace size
  MAINTAINERS: Add Jan Kara for filesystem DAX
  MAINTAINERS: update Ross Zwisler's email address
  tools/testing/nvdimm: Fix support for emulating controller temperature
  tools/testing/nvdimm: Make DSM failure code injection an override
  acpi, nfit: Prefer _DSM over _LSR for namespace label reads
  libnvdimm: Introduce locked DIMM capacity support

dm writecache: fix a crash due to reading past end of dirty_bitmap

2018-08-16T17:43:01+00:00

wc->dirty_bitmap_size is in bytes so must multiply it by 8, not by
BITS_PER_LONG, to get number of bitmap_bits.

Fixes crash in find_next_bit() that was reported:
https://bugzilla.kernel.org/show_bug.cgi?id=200819

Reported-by: edo.rus@gmail.com
Fixes: 48debafe4f2f ("dm: add writecache target")
Cc: stable@vger.kernel.org # 4.18
Signed-off-by: Mikulas Patocka 
Signed-off-by: Mike Snitzer

md/dm-writecache: Don't request pointer dummy_addr when not required

2018-07-30T16:40:04+00:00

Function persistent_memory_claim doesn't need to get local pointer
dummy_addr from direct_access. Using NULL instead of having to pass
in a useless local pointer that caller then just throw away.

Suggested-by: Ross Zwisler 
Signed-off-by: Huaisheng Ye 
Reviewed-by: Ross Zwisler 
Acked-by: Mike Snitzer 
Signed-off-by: Dave Jiang

dm writecache: report start_sector in status line

2018-07-27T19:28:58+00:00

Fixes: d284f8248c7 ("dm writecache: support optional offset for start of device")
Signed-off-by: Mikulas Patocka 
Signed-off-by: Mike Snitzer

dm writecache: support optional offset for start of device

2018-07-02T20:14:02+00:00

Add an optional parameter "start_sector" to allow the start of the
device to be offset by the specified number of 512-byte sectors.  The
sectors below this offset are not used by the writecache device and are
left to be used for disk labels and/or userspace metadata (e.g. lvm).

Signed-off-by: Mikulas Patocka 
Signed-off-by: Mike Snitzer

dm writecache: use 2-factor allocator arguments

2018-06-22T18:51:12+00:00

This adjusts the allocator calls to use the 2-factor argument style, as
already done treewide for better defense against allocator overflows.

Signed-off-by: Kees Cook 
[snitzer: tweaked code to leave assignment in a test alone]
Signed-off-by: Mike Snitzer

dm: add writecache target

2018-06-08T15:59:51+00:00

The writecache target caches writes on persistent memory or SSD.
It is intended for databases or other programs that need extremely low
commit latency.

The writecache target doesn't cache reads because reads are supposed to
be cached in page cache in normal RAM.

If persistent memory isn't available this target can still be used in
SSD mode.

Signed-off-by: Mikulas Patocka 
Signed-off-by: Colin Ian King  # fix missing goto
Signed-off-by: Ross Zwisler  # fix compilation issue with !DAX
Signed-off-by: Dan Carpenter  # use msecs_to_jiffies
Acked-by: Dan Williams  # reworks to unify ARM and x86 flushing
Signed-off-by: Mike Snitzer