diff options
| author | Dan Williams <[email protected]> | 2018-07-14 04:50:16 +0000 |
|---|---|---|
| committer | Dave Jiang <[email protected]> | 2018-07-23 17:38:06 +0000 |
| commit | c2a7d2a115525d3501d38e23d24875a79a07e15e (patch) | |
| tree | df178de827dbda4bce219d4bfb812581d4883b53 /tools/perf/scripts/python/syscall-counts.py | |
| parent | mm, memory_failure: Collect mapping size in collect_procs() (diff) | |
| download | kernel-c2a7d2a115525d3501d38e23d24875a79a07e15e.tar.gz kernel-c2a7d2a115525d3501d38e23d24875a79a07e15e.zip | |
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 <[email protected]>
Cc: Matthew Wilcox <[email protected]>
Cc: Ross Zwisler <[email protected]>
Cc: Jan Kara <[email protected]>
Signed-off-by: Dan Williams <[email protected]>
Signed-off-by: Dave Jiang <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions