Revision 9f141d6ef6258a3a37a045842d9ba7e68f368956 authored by Jan Kara on 19 October 2016, 12:34:31 UTC, committed by Dan Williams on 27 December 2016, 04:29:25 UTC
Currently ->iomap_begin() handler is called with entry lock held. If the filesystem held any locks between ->iomap_begin() and ->iomap_end() (such as ext4 which will want to hold transaction open), this would cause lock inversion with the iomap_apply() from standard IO path which first calls ->iomap_begin() and only then calls ->actor() callback which grabs entry locks for DAX (if it faults when copying from/to user provided buffers). Fix the problem by nesting grabbing of entry lock inside ->iomap_begin() - ->iomap_end() pair. Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
1 parent f449b93
| File | Mode | Size |
|---|---|---|
| mpr.HEX | -rw-r--r-- | 9.7 KB |
| usa18x.HEX | -rw-r--r-- | 15.3 KB |
| usa19.HEX | -rw-r--r-- | 9.7 KB |
| usa19qi.HEX | -rw-r--r-- | 9.7 KB |
| usa19qw.HEX | -rw-r--r-- | 15.3 KB |
| usa19w.HEX | -rw-r--r-- | 15.3 KB |
| usa28.HEX | -rw-r--r-- | 15.8 KB |
| usa28x.HEX | -rw-r--r-- | 15.3 KB |
| usa28xa.HEX | -rw-r--r-- | 15.3 KB |
| usa28xb.HEX | -rw-r--r-- | 15.3 KB |
| usa49w.HEX | -rw-r--r-- | 15.9 KB |
| usa49wlc.HEX | -rw-r--r-- | 16.0 KB |
Computing file changes ...
