diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2018-07-13 21:50:01 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-09-09 10:32:41 +0200 |
| commit | 5ad671c8520d49ef4d50f8d30a3f82288d9289a5 (patch) | |
| tree | 91bbef68b7ee4211ed3a68df3b50f6ad41aa38a0 /kernel | |
| parent | ff1663fc9483e131f674db8b2f42f9a99460ae50 (diff) | |
mm, dev_pagemap: Do not clear ->mapping on final put
commit 2fa147bdbf672c53386a8f5f2c7fe358004c3ef8 upstream.
MEMORY_DEVICE_FS_DAX relies on typical page semantics whereby ->mapping
is only ever cleared by truncation, not final put.
Without this fix dax pages may forget their mapping association at the
end of every page pin event.
Move this atypical behavior that HMM wants into the HMM ->page_free()
callback.
Cc: <stable@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>
Cc: Jérôme Glisse <jglisse@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
Fixes: d2c997c0f145 ("fs, dax: use page->mapping...")
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Jérôme Glisse <jglisse@redhat.com>
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel')
| -rw-r--r-- | kernel/memremap.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/kernel/memremap.c b/kernel/memremap.c index 38283363da06..cfb750105e1e 100644 --- a/kernel/memremap.c +++ b/kernel/memremap.c @@ -355,7 +355,6 @@ void __put_devmap_managed_page(struct page *page) __ClearPageActive(page); __ClearPageWaiters(page); - page->mapping = NULL; mem_cgroup_uncharge(page); page->pgmap->page_free(page, page->pgmap->data); |