On Mon, 1 Jul 2019 19:10:38 +0530 "Aneesh Kumar K.V"
Architectures like powerpc use different address range to map
and vmalloc range. The memunmap() check used by the nvdimm layer was
wrongly using is_vmalloc_addr() to check for ioremap range which fails for
ppc64. This result in ppc64 not freeing the ioremap mapping. The side effect
of this is an unbind failure during module unload with papr_scm nvdimm driver
The patch applies to 5.1. Does it need a Fixes: and a Cc:stable?