summaryrefslogtreecommitdiff
path: root/drivers/target
diff options
context:
space:
mode:
authorMike Christie <mchristi@redhat.com>2017-05-02 23:57:05 -0500
committerNicholas Bellinger <nab@linux-iscsi.org>2017-05-04 20:01:41 -0700
commitd906d8af28e524bfa62c49cb2315f6ccdb910938 (patch)
tree4dc3c3e5801ed5d22ba2e7e464136dd5c69ff6d6 /drivers/target
parent46861cdd80e1a862dc65d10833a1450861fabef7 (diff)
tcmu: fix module removal due to stuck thread
We need to do a kthread_should_stop to check when kthread_stop has been called. This was a regression added in b6df4b79a5514a9c6c53533436704129ef45bf76 tcmu: Add global data block pool support so not sure if you wanted to merge it in with that patch or what. Signed-off-by: Mike Christie <mchristi@redhat.com> Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'drivers/target')
-rw-r--r--drivers/target/target_core_user.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/target/target_core_user.c b/drivers/target/target_core_user.c
index 89b75ce563d8..9045837f748b 100644
--- a/drivers/target/target_core_user.c
+++ b/drivers/target/target_core_user.c
@@ -1560,6 +1560,9 @@ static int unmap_thread_fn(void *data)
schedule();
finish_wait(&unmap_wait, &__wait);
+ if (kthread_should_stop())
+ break;
+
mutex_lock(&root_udev_mutex);
list_for_each_entry(udev, &root_udev, node) {
mutex_lock(&udev->cmdr_lock);