diff options
| author | Matthew Wilcox <willy@infradead.org> | 2018-11-16 14:37:06 -0500 |
|---|---|---|
| committer | Matthew Wilcox <willy@infradead.org> | 2018-11-16 16:38:50 -0500 |
| commit | c5bbd4515a05f8acb7e6ab6297044a529762cbf5 (patch) | |
| tree | d48233766456a2fb166f583c87d2fb4b36d618ec /fs/file.c | |
| parent | 7ae2ea7dc45e8250a74cfaaecdce578427669ae5 (diff) | |
| download | linux-c5bbd4515a05f8acb7e6ab6297044a529762cbf5.tar.bz2 | |
dax: Reinstate RCU protection of inode
For the device-dax case, it is possible that the inode can go away
underneath us. The rcu_read_lock() was there to prevent it from
being freed, and not (as I thought) to protect the tree. Bring back
the rcu_read_lock() protection. Also add a little kernel-doc; while
this function is not exported to modules, it is used from outside dax.c
Reported-by: Dan Williams <dan.j.williams@intel.com>
Fixes: 9f32d221301c ("dax: Convert dax_lock_mapping_entry to XArray")
Signed-off-by: Matthew Wilcox <willy@infradead.org>
Diffstat (limited to 'fs/file.c')
0 files changed, 0 insertions, 0 deletions