diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2018-07-14 07:50:16 +0300 |
|---|---|---|
| committer | Dave Jiang <dave.jiang@intel.com> | 2018-07-23 20:38:06 +0300 |
| commit | c2a7d2a115525d3501d38e23d24875a79a07e15e (patch) | |
| tree | df178de827dbda4bce219d4bfb812581d4883b53 /mm | |
| parent | ae1139ece126b8eb6d0770094fbac43ea928d9d9 (diff) | |
| download | linux-c2a7d2a115525d3501d38e23d24875a79a07e15e.tar.xz | |
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 'mm')
0 files changed, 0 insertions, 0 deletions