diff options
| author | Matthew Wilcox <[email protected]> | 2018-11-16 19:37:06 +0000 |
|---|---|---|
| committer | Matthew Wilcox <[email protected]> | 2018-11-16 21:38:50 +0000 |
| commit | c5bbd4515a05f8acb7e6ab6297044a529762cbf5 (patch) | |
| tree | d48233766456a2fb166f583c87d2fb4b36d618ec /lib/test_xarray.c | |
| parent | dax: Make sure the unlocking entry isn't locked (diff) | |
| download | kernel-c5bbd4515a05f8acb7e6ab6297044a529762cbf5.tar.gz kernel-c5bbd4515a05f8acb7e6ab6297044a529762cbf5.zip | |
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 <[email protected]>
Fixes: 9f32d221301c ("dax: Convert dax_lock_mapping_entry to XArray")
Signed-off-by: Matthew Wilcox <[email protected]>
Diffstat (limited to 'lib/test_xarray.c')
0 files changed, 0 insertions, 0 deletions