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
History
File Mode Size
Kconfig -rw-r--r-- 2.4 KB
Makefile -rw-r--r-- 412 bytes
aha152x_core.c -rw-r--r-- 61 bytes
aha152x_stub.c -rw-r--r-- 6.7 KB
fdomain_core.c -rw-r--r-- 38 bytes
fdomain_stub.c -rw-r--r-- 5.8 KB
nsp_cs.c -rw-r--r-- 45.0 KB
nsp_cs.h -rw-r--r-- 12.0 KB
nsp_debug.c -rw-r--r-- 5.9 KB
nsp_io.h -rw-r--r-- 6.9 KB
nsp_message.c -rw-r--r-- 2.1 KB
qlogic_stub.c -rw-r--r-- 9.3 KB
sym53c500_cs.c -rw-r--r-- 23.2 KB

back to top