"Aneesh Kumar K.V" <aneesh.kumar(a)linux.ibm.com> writes:
Andrew Morton <akpm(a)linux-foundation.org> writes:
> On Mon, 1 Jul 2019 19:10:38 +0530 "Aneesh Kumar K.V"
>> Architectures like powerpc use different address range to map ioremap
>> 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?
Actually, we want it to be backported to an older kernel possibly one
that added papr-scm driver, b5beae5e224f ("powerpc/pseries: Add driver
for PAPR SCM regions"). But that doesn't apply easily. It does apply
without conflicts to 5.0
Don't worry about where it applies or doesn't, just tag it with the
correct Fixes: and stable versions and then if it doesn't backport
cleanly then we deal with that later.