path: root/mm/memory-failure.c
diff options
authorDan Williams <dan.j.williams@intel.com>2018-07-13 21:50:16 -0700
committerDave Jiang <dave.jiang@intel.com>2018-07-23 10:38:06 -0700
commitc2a7d2a115525d3501d38e23d24875a79a07e15e (patch)
treedf178de827dbda4bce219d4bfb812581d4883b53 /mm/memory-failure.c
parentmm, memory_failure: Collect mapping size in collect_procs() (diff)
filesystem-dax: Introduce dax_lock_mapping_entry()
In preparation for implementing support for memory poison (media error) handling via dax mappings, implement a lock_page() equivalent. Poison error handling requires rmap and needs guarantees that the page->mapping association is maintained / valid (inode not freed) for the duration of the lookup. In the device-dax case it is sufficient to simply hold a dev_pagemap reference. In the filesystem-dax case we need to use the entry lock. Export the entry lock via dax_lock_mapping_entry() that uses rcu_read_lock() to protect against the inode being freed, and revalidates the page->mapping association under xa_lock(). Cc: Christoph Hellwig <hch@lst.de> Cc: Matthew Wilcox <willy@infradead.org> Cc: Ross Zwisler <ross.zwisler@linux.intel.com> Cc: Jan Kara <jack@suse.cz> Signed-off-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions