summaryrefslogtreecommitdiffstats
path: root/module/splat
diff options
context:
space:
mode:
authorBrian Behlendorf <[email protected]>2015-02-25 10:29:02 -0800
committerBrian Behlendorf <[email protected]>2015-03-03 10:18:24 -0800
commitd0d5dd714424365a4da0d887cb641cb2f0ae8844 (patch)
treea408c3f3bafc5f752e83cdacf4564051e34d98f4 /module/splat
parent5f920fbee1fd1838bad2d5a262041a3a171b6834 (diff)
Add MUTEX_FSTRANS mutex type
There are regions in the ZFS code where it is desirable to be able to be set PF_FSTRANS while a specific mutex is held. The ZFS code could be updated to set/clear this flag in all the correct places, but this is undesirable for a few reasons. 1) It would require changes to a significant amount of the ZFS code. This would complicate applying patches from upstream. 2) It would be easy to accidentally miss a critical region in the initial patch or to have an future change introduce a new one. Both of these concerns can be addressed by adding a new mutex type which is responsible for managing PF_FSTRANS, support for which was added to the SPL in commit 9099312 - Merge branch 'kmem-rework'. Signed-off-by: Brian Behlendorf <[email protected]> Signed-off-by: Tim Chase <[email protected]> Issue #435
Diffstat (limited to 'module/splat')
-rw-r--r--module/splat/splat-atomic.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/module/splat/splat-atomic.c b/module/splat/splat-atomic.c
index a270dc42f..e94f42f00 100644
--- a/module/splat/splat-atomic.c
+++ b/module/splat/splat-atomic.c
@@ -145,7 +145,7 @@ splat_atomic_test1(struct file *file, void *arg)
ap.ap_magic = SPLAT_ATOMIC_TEST_MAGIC;
ap.ap_file = file;
- mutex_init(&ap.ap_lock, SPLAT_ATOMIC_TEST1_NAME, NULL, NULL);
+ mutex_init(&ap.ap_lock, SPLAT_ATOMIC_TEST1_NAME, MUTEX_DEFAULT, NULL);
init_waitqueue_head(&ap.ap_waitq);
ap.ap_atomic = SPLAT_ATOMIC_INIT_VALUE;
ap.ap_atomic_exited = 0;